Troubleshooting

Start with the server's Logs tab: every call shows its status, duration and error. The Playground repeats a call without involving an AI client.

The first call is slow

The gateway scales to zero when idle, so the first request after a quiet spell can take a few seconds while it starts. Later calls are fast. If a client gives up on the first connection, retry it.

401 Unauthorized

The client's credentials were refused.

• API key: check that it's sent as Authorization: Bearer mcpk_live_… (not in the URL), belongs to this server and hasn't been revoked. Lost keys can't be shown again; create a new one.
• OAuth: sign in again from the client (/mcp → Authenticate in Claude Code, Needs login in Cursor, reconnect the connector in Claude).

If the tool call itself returns "The API session for this server expired", it's your API refusing the call: open the server in the dashboard and Sign in again (see upstream sign-in).

403 Forbidden

• "Server paused": only one server per account is active at a time. Resume it from the dashboard.
• "This account doesn't own this MCP server": with OAuth, sign in with the account that created it.
• "Origin not allowed": a browser page called the MCP URL directly; use an MCP client.

A 403 inside a tool result comes from your API: check the credentials you gave SourceMCP for it.

429 Too many requests

A rate limit was hit: 60 tool calls per minute or 2,000 per day per server, or 120 MCP requests per minute per credential. The response carries Retry-After; wait that long. Your usage is on the limits page. A 429 inside a tool result is your API's own rate limit.

An endpoint is missing or greyed out

Some operations can't become tools yet, and the endpoint list says why:

• request bodies of type multipart/form-data (file uploads), application/octet-stream or other non-JSON types;
• the login and refresh endpoints of a server that signs in to its API (SourceMCP calls those itself);
• deprecated operations start unselected but can be turned on.

Tools don't show up in the client

• Check the server is active and has active tools on the Tools tab (at most 100).
• Restart or reconnect the client: many clients read the tool list only when they connect.
• Clients that only start local servers need mcp-remote.

Calls time out

Calls to your API stop after the server's timeout (30 seconds by default, up to 60 in Settings). Slow endpoints may need a higher timeout, or narrower arguments such as a page size.

Still stuck

Email [email protected] with what you tried and any error IDs from the dashboard. We read every message during the beta.