EchoSign in

Echo MCP

Connect Echo to Claude, Codex, Cursor, and other MCP clients so they can read your cloud-synced meetings and transcripts, manage reusable artifact definitions in your Echo account, and propose meeting edits for your review.

Quick setup

MCP is the plug that lets your AI client talk straight to Echo. Pick your app below, add Echo, then sign in once in your browser.

What you need

  • An Echo account
  • An app that supports remote HTTP MCP connections
  • A browser for the one-time Echo sign-in flow

Claude

Open Customize → Connectors and add a custom connector named Echo. On Team or Enterprise plans, an owner must add it for the organization first.

Add Echo to Claude

Using Claude Code? Run this instead:

claude mcp add --transport http echo https://mcp.echoecho.ai/mcp

Connect your account

  1. Save or add the Echo connection.
  2. Choose Connect, or ask the app to use Echo. Your browser should open the first time the app connects.
  3. Sign in to Echo and approve the requested access.
  4. Return to your AI app and try one of the prompts below.

Try it

Once Echo is connected, test it with a simple prompt like this:

Use Echo to show my 5 most recent meetings.
Search my Echo transcripts for "pricing discussion".
Find the meeting where we discussed the launch plan, then read its transcript.
Create a batch artifact definition named Customer follow-up with instructions to draft a concise follow-up email, and leave default_on false.
Create a live artifact definition that maintains a decision log during meetings.
Propose a clearer summary for my last meeting, then show me the pending proposal.

What Echo can do

  • Meetings available to the Echo account you connected
  • Your meeting list and meeting details
  • Canonical meeting notes and participants
  • Transcript search results and transcript pages
  • List and read reusable artifact definitions owned by your account
  • Create, update, and delete those definitions, including their instructions, learned instructions, batch or live execution_timing, and default_on setting
  • after_meeting definitions run as batch artifacts after capture; livedefinitions update during active capture. default_on controls automatic batch generation and is ignored while a definition is live.
  • Propose edits to meeting summaries and transcript corrections. A proposal is a pending, reviewable change stored in your Echo account — nothing in your meeting data changes until a proposal is applied.
  • Applying or discarding a proposal happens only through the explicit apply_edit_proposal and discard_edit_proposal tools, which are marked destructive. We recommend keeping your client’s tool approval on for apply so you confirm each applied edit.

Browse the full tool reference

Troubleshooting

  • If Echo does not appear after you add it, restart the AI app and check that the server URL is exact.
  • If sign-in does not start, disconnect and re-add Echo using https://mcp.echoecho.ai/mcp.
  • If you see the wrong data, disconnect Echo, sign out in your browser, then reconnect with the right account.

Questions or issues? Send us feedback!