Echo’s API, webhooks and MCP connector
Connect Echo to your own software. Upload files and read transcripts with the API, get every finished meeting in a webhook and let your AI assistant look through your meetings.
What Echo does with API, webhooks and MCP
- An API to upload files, list them, check their status, read the summary and transcript, export them and delete them.
- Keys that act on your behalf; Echo only stores their fingerprint and you can revoke them at any time.
- Webhooks with JSON signed with HMAC-SHA256 every time a transcription finishes or fails.
- A read-only MCP connector: your assistant can ask your meetings questions, search them, list them and read one in full.
- Up to 120 requests per minute per key.
How to connect it
- 1
Create a key
In Settings, API, give it a name and click “Create a key”. Copy it: it won’t be shown again.
- 2
Use the API or MCP
Send the key in the Authorization header. For the connector, open “Use Echo from Claude, ChatGPT or another assistant (MCP)” and follow the instructions.
- 3
Add a webhook
In Settings, Integrations, click “Add Webhook”, enter your https address and keep the signing key.
Frequently asked questions
What can the MCP connector do?
Only read: ask your meetings questions, search, list meetings and workspaces and read a meeting. It doesn’t change anything.
How do I check a webhook comes from Echo?
Each delivery carries the X-Echo-Signature header with an HMAC-SHA256 of the timestamp and body, made with the key you see when you create it.
Does the key work for all of Echo?
No. It works for the public API and the MCP connector; managing keys or integrations requires signing in.
Which plan do I need?
The API and the MCP connector are on the Pro plan.
Try it with your next meeting.
Create your account in a minute or ask us for a demo for your team.
