Any MCP client

EchoSift exposes a standard MCP server over HTTP (Streamable HTTP transport). Any client that supports this transport can connect.

Server URL

https://mcp.echosift.io/mcp

Auth modes

OAuth 2.1 PKCE (recommended)

If your client supports MCP OAuth 2.1, point it at the server URL and let it discover the authorization server from the well-known metadata:

GET https://mcp.echosift.io/.well-known/oauth-authorization-server

The client receives an access token after the browser-based sign-in flow. No manual key management needed.

Bearer API key (fallback)

If your client does not support OAuth, generate an API key from Settings > Integrations in EchoSift and send it in every request:

Authorization: Bearer es_YOUR_KEY_HERE

Keys have the format es_<prefix>_<secret> and require a Pro subscription.

Health check

curl https://mcp.echosift.io/health

Expected response: {"status":"ok"} (or similar).

Tools/list (after auth)

curl -X POST https://mcp.echosift.io/mcp \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

You should receive 8 tool definitions.

Rate limit

60 requests per minute per user. See Limits and fair use for more.