Troubleshooting

Common hosted MCP connection and tool-discovery problems.

OAuth loops or never completes

Confirm you are using https://backend.jupid.com/mcp — the URL must point at the backend host and end with /mcp. If the client keeps opening the sign-in flow, remove the Jupid MCP connection from the client, add it again, and complete OAuth in the same browser profile where you can sign in to Jupid.

Client shows no Jupid tools

Check the client's MCP status screen. The server should be connected with Streamable HTTP transport and OAuth auth. If the client was already open when you added the server, restart the client and reconnect Jupid.

Client says the endpoint is wrong

Do not use the Jupid app URL (app.jupid.com) as the server URL. The MCP endpoint lives on the backend host: https://backend.jupid.com/mcp.

Answers do not use financial data

The assistant must call Jupid tools before answering finance questions. Ask a setup question such as "What data is connected to Jupid?" and check whether the client reports a Jupid tool call. If no data is connected in Jupid, connect an account in the web app first.

A tool is unavailable

Make sure the client is connected to the hosted Jupid MCP server, not an old local package or workspace config. If the client caches tool lists, reconnect the server after Jupid adds new tools.

Disconnect or revoke access

Remove the Jupid server from the client's MCP configuration. Access tokens expire on their own within one hour; refresh tokens stop working once the server is removed from the client.

Still stuck

Email slava@jupid.com with the client name, the step that fails, and any error the client shows.