Skip to main content
Assistants connect by signing in to Echod - OAuth, with nothing to copy but the server URL. The first time your assistant connects, it opens Echod in your browser, where you sign in and approve it.
The fastest way to connect is from the app: Settings > MCP Server shows the server URL and the exact steps or snippet for your assistant. This page explains the same setup in general terms.

​
1. Get the server URL

In Echod, open Settings > MCP Server and copy the server URL (it ends in /mcp). That is all your assistant needs - no token.

​
2. Add it to your assistant

A typical JSON entry contains only the address:
Do not add an Authorization header for an assistant that signs in - a configured header can stop the sign-in from working. Headers are only for scripts and automation.

​
3. Approve it in your browser

When the assistant first connects, Echod opens a consent page that shows which app is asking and how far Echod could verify its identity. Approving gives the assistant read-only access to every project you can open; it cannot change anything. Approve only a request you just started yourself. Approved assistants appear under Connected apps in Settings > MCP Server, with when each was connected and last used. You can disconnect one at any time; it loses access on its next request.

​
4. Try it

Restart your client if it reads configuration at startup, then ask:
List my Echod projects
If your projects come back, you are connected.

​
Scripts and automation

Assistants sign in, so access tokens are only for what has no browser to sign in with: scripts, CI and agents you build yourself.
  1. In Echod, open Settings > MCP Server and create an access token under For scripts and automation. Optionally give it an expiry (30, 60 or 90 days, or none).
  2. Copy the token (it starts with echod_pat_). It is shown once; if you lose it, revoke it and create a new one.
  3. Send it as a bearer header to the server URL: Authorization: Bearer echod_pat_....
The token acts as you: the script sees the projects you can open, read-only. Create one per script, so you can revoke it without breaking the others. The same route works for an MCP client that cannot sign in: configure the server URL with that Authorization header.

​
Troubleshooting

  • The browser never opens to sign in: most clients read MCP configuration at startup; restart the client after adding the server. If the client cannot sign in to MCP servers at all, use an access token as described above.
  • “This request has expired” on the consent page: a connection request lasts ten minutes and works once. Go back to your assistant and connect again.
  • The assistant lost access: it was disconnected under Connected apps, or its sign-in lapsed. Connect and approve it again.
  • 401 or “unauthorized” with a token: the token is missing, mistyped, expired or revoked. Create a new one in Settings > MCP Server.
  • 429 or “rate limited”: the response includes a retry delay; your assistant retries after it. Sustained bursts across many parallel calls are the usual cause.