MCP troubleshooting

Common hosted MCP connection and tool-discovery problems.

OAuth loops or never completes

1. Confirm the server URL is https://backend.jupid.com/mcp.
2. Confirm you can sign in to Jupid in the browser profile opened by the client. Complete both sign-in and the Jupid authorization prompt.
3. If the client keeps reopening authorization, clear its saved Jupid OAuth credentials, remove the server entry, and add it again using the client quickstart.

Access tokens last one hour; refresh tokens last up to 30 days. A client that cannot refresh, or whose refresh token has expired, needs a new sign-in.

Client shows no Jupid tools

Check the client's MCP status screen for a successful OAuth connection over Streamable HTTP. Enable Jupid for the current conversation or agent and check that workspace policy allows it. The server exposes 17 tools, although a client or administrator may enable only a subset. Reload or restart the client if it has not picked up a newly added server.

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.

Opening that URL in a browser is not a connection test. The endpoint handles MCP requests, so a browser GET can return an authentication or method error. Verify it from the client's MCP status screen and a real tool call.

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.

If results belong to a different business, select the intended active business in Jupid and repeat the tool call. MCP resolves that selection on every call. For incomplete search results, check total and hasMore and narrow the query. Reports include filed transactions only; recently uploaded data may still be processing.

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.

For a published ChatGPT app, an administrator may need to refresh and publish its tool definitions; reconnecting alone does not update its saved tool list. See OpenAI's current app-management instructions.

If a tool appears but returns an error, check its access requirements. Account deletion requires the active business's owner. Billing status shows your own subscription for both owners and members. Demo users cannot use the four ingestion tools, and upserts require a connected API source. Company access-management tools are not available to external OAuth clients.

Disconnect or revoke access

Use the client's disconnect or logout control to clear its saved Jupid OAuth credentials, then remove the Jupid server entry. In Codex, run codex mcp logout jupid before codex mcp remove jupid.

Removing configuration stops that client from using the connection; it does not invalidate a token already issued by Jupid. Access tokens expire within one hour and refresh tokens within 30 days of issuance. Jupid currently has no per-client token-revocation control. Contact support if credentials may have been exposed.

Still stuck

Email slava@jupid.com with the client name and version, the step or tool that fails, the time of the failure, and the displayed error. Leave tokens and financial payloads out of the report.