Why won't my MCP client connect?
Automation · Updated Jun 22, 2026
Check whether your client supports remote MCP, confirm the server URL, then choose OAuth or token auth based on the client.
First confirm that your client supports remote or Streamable HTTP MCP servers. If it supports OAuth, add the Canopy MCP server URL and approve access in the browser. See OAuth for MCP clients for the browser approval flow.
If the client only supports tokens, create a workspace API token and pass it as a Bearer token in the Authorization header. Make sure you are using a token from the workspace you want the agent to read. See connect with a token for examples.
If the client never opens a browser, asks for a token unexpectedly, or returns an auth error, revoke the old connection and try again from Workspace API settings.
Related articles
How does MCP access work?
AutomationCanopy exposes a read-only remote MCP server so agents can query maps, services, spend, and dependencies.
What should I do if I hit an API or AI limit?
AutomationWait for the reset window, reduce repeated requests, or get support if your workspace needs a higher operational ceiling.
Why is Canopy AI disabled?
AutomationCanopy AI is a Pro feature, but some dashboard AI surfaces may stay disabled while the feature is still being prepared.