MCP Connection Issues

Claude Desktop not connecting

• Config syntax: Make sure the JSON in your config file is valid. A missing comma or quote will prevent loading.
• Restart required: After adding or changing the config, quit and restart Claude Desktop completely.
• Node.js: The config runs npx mcp-remote, so Node.js must be installed.
• API key: Check that your API key works with a curl command first. See API Key Not Working.

Claude Code not connecting

• Run claude mcp list to check that the server was added.
• Check that you used --transport http and that the URL is exactly https://statusforge.net/api/mcp.

Asked to sign in with OAuth

The Forge MCP server uses API keys only. It has no OAuth sign-in. If your client starts an OAuth sign-in, or shows an error that mentions OAuth, the server rejected your API key. Check the key and the Authorization header, then restart the client.

"Service temporarily unavailable, please retry shortly"

The server couldn't check your key in time. This is temporary. Wait a few seconds and try again. You don't need a new key.

Tool calls returning errors

• ChangeForge is disabled for this account (or StatusForge or HelpForge): All tools always appear, but tools for a product that's turned off fail. Turn the product on in Settings > Products & Plans.
• Invalid id: must be a valid UUID: The AI may have made up an ID. Ask it to list resources first, then use the returned IDs.
• Validation failed: A value is missing or not accepted. When you update an incident, include a status, even if it isn't changing.
• rate_limited: You've hit your key's rate limit. Wait up to 1 minute, then retry.