Jupid MCP
Connect external AI agents to Jupid financial data through hosted MCP.
Jupid MCP is a hosted Model Context Protocol endpoint for external AI agents. It lets MCP-capable clients answer questions using the same user-scoped Jupid data available in the app.
Use it when you want an assistant such as Claude, Codex, Cursor, ChatGPT, VS Code with GitHub Copilot, or Windsurf to inspect Jupid financial context without exporting data manually.
You need a Jupid account, access to the business you want to work with, and a client with remote MCP and OAuth support. Start with the client quickstart, then confirm the assistant can list your connected accounts.
How it works
The hosted MCP server URL is stable for all users:
https://backend.jupid.com/mcpThe endpoint uses Streamable HTTP (JSON responses) and OAuth with PKCE S256. When a client first connects, Jupid opens a browser sign-in flow and authorizes the client for the signed-in user — no API keys. Access tokens expire after one hour. Clients that support token refresh can renew access for up to 30 days before a new sign-in is needed.
The MCP server resolves the authorized user's current active Jupid business for each call. A connected client can only access data allowed by that membership.
Switching the active business in Jupid changes the business used by subsequent MCP calls. The HTTP API uses an explicit business ID instead.
What agents can answer
- Accounts, balances, integrations, and sync status.
- Transactions and counterparties — vendors, clients, investors, contractors — by date, amount, category, or review state.
- Cash-flow and Schedule C P&L reports by period and category tree.
- Open questions that need your context before Jupid can keep processing.
See MCP tools for the full catalog with inputs and outputs.
Safety boundaries
Read tools return structured summaries and app links. Account numbers are masked and search results are bounded.
Twelve of the seventeen tools are read-only. answerOutstandingIssue saves
an answer to an open issue. upsertAccounts, upsertTransactions,
deleteAccount, and deleteTransaction synchronize financial data through
the same operations as the HTTP API. Account deletion requires
the business owner; demo users cannot use the four ingestion tools.
getBillingStatus returns the signed-in person's own subscription, including
for business members. Account and transaction upserts require an existing,
connected API source created through the HTTP API.
Company access management is unavailable to external MCP clients. Use the company's Access page; partner-provided access is managed through the partner. The Box has a separate company-bound connection and requires a verified owner's request for access changes. Changing your active business does not retarget The Box.
Direct recategorization, category editing, file upload, provider pull-sync triggers, and billing changes remain outside this tool catalog.
Privacy and support
Tool results are sent to the MCP client you connect and may become part of that client's AI conversation. Its provider's privacy and retention policies apply to that use. Jupid's normal processing, including AI categorization triggered by uploads or context answers, is covered by the Jupid Privacy Policy and Terms of Service.
For help, email slava@jupid.com or start with Troubleshooting.