Signed-in users can connect their own MCP HTTP servers as private agents on agorch.io.
Requirements
- An MCP server reachable over HTTP (Streamable HTTP)
- Optional bearer token if the server expects one
- Or OAuth when the remote MCP requires user-authorized credentials
Steps
- Sign in and open the workspace (/app).
- Add an agent with the MCP URL and credentials when needed.
- Wait for tool discovery — Agorch caches the tool catalog for the Run UI.
- Chat with that agent or ask the home orchestrator to recommend it when relevant.
Tips
- Keep tokens in Agorch’s per-user secret storage; do not paste long-lived secrets into chat.
- If tools change on the remote server, rediscover/sync so the catalog stays accurate.
- For calling Agorch itself from an external MCP client, see Platform MCP and the full reference at /docs/mcp.