Connection and sign-in troubleshooting
Fix the most common MCP connection and OAuth problems.
The browser sign-in did not finish
Start the connection again from Connections and complete authorization in the browser window opened by your AI tool. Ensure you sign in to the SpecMCP account that belongs to the intended organization. If a stale connection remains, revoke it first and reconnect.
The client cannot see SpecMCP
Confirm the MCP URL was copied exactly, including /mcp. Restart or reload the client after changing its configuration. For Claude Code and Codex, use /mcp to inspect the registered server; for VS Code, enable the server in the Copilot tools picker.
A token-based connection fails
Generate a new personal access token and replace the old value. Tokens are shown only once, so a partially copied or lost token cannot be recovered. A SpecMCP personal access token begins with gsp_; make sure the header is exactly Authorization: Bearer YOUR_TOKEN and that the full value was pasted with no extra quotes or whitespace.
SpecMCP says it is active on another device
Each seat allows one concurrent MCP session per tool. If you connect the same tool from a second device while the first is still active, the call is rejected with a message that SpecMCP is active elsewhere. Run the same call again to transfer the active session to the current device. The previous device reclaims the session the next time it runs a call. If you need genuinely parallel access, add another seat from Billing.
I need to disconnect a tool
Go to Connections, find the connected tool, and revoke it. For a shared Notion connection, an organization administrator must revoke its token from Team.