My MCP client won’t connect
Check client setup, renew the connection, and resolve project or scope errors.
Why it happens
An expired or revoked connection needs a new approval. A connection can also work while still pointing at the wrong project or lacking the scope for a particular tool.
What to do
- First connection? Compare your configuration with the setup for your MCP client.
- Asked to sign in again? Reconnect and approve the connection for the intended project. If an old connection points at another project, revoke it in Settings → MCP Connections.
- Seeing
INSUFFICIENT_SCOPE? Review the tool’s required scope, then reconnect with the minimum access you need. Your project role must also allow the action.
Check the result
Confirm the connection appears under Settings → MCP Connections. If you granted list access, ask the client to list masked keys and check that they belong to the expected project.
Still stuck? Contact support with the error and the steps you tried. Remove secret values before sending.
Was this page helpful?