Any MCP client
Last verified: 2026-07-21
The server speaks MCP over Streamable HTTP with OAuth 2.1 (PKCE, dynamic client registration, RFC 9728 discovery). Any client that supports those two things can connect.
What your client needs
| Setting | Value |
|---|---|
| Server / endpoint URL | https://mcp.manyreach.com/mcp |
| Transport | Streamable HTTP (POST + optional SSE GET) |
| Auth | OAuth 2.1 with PKCE — discovered automatically |
Steps
- Add a remote/HTTP MCP server with the URL
https://mcp.manyreach.com/mcp - Your client fetches the protected-resource metadata for
https://mcp.manyreach.com/mcpand is redirected to the authorization server athttps://mcp-auth.manyreach.com— a browser window opens. - Paste your Manyreach API key into the authorization page and approve. The key is checked once and exchanged for a short-lived token; the AI never sees the key itself.
- Done — the client holds a token and refreshes it automatically.
Verify
Ask your assistant to "describe the Manyreach catalog" — it should call the describe tool and
list resources like campaign, prospect, and sender.
Troubleshooting
- No browser window opened — your client may not support OAuth for remote MCP servers; check its documentation for "remote MCP" or "HTTP MCP server" support.
- 401 after connecting — the token may have expired mid-session; disconnect and reconnect the server in your client.
- Key rejected on the authorization page — verify the API key in the Manyreach web app under API & Integrations, and that your plan includes API access.