Model Context Protocol (MCP)

Sure includes an MCP server that lets compatible AI assistants use the financial data and tools available to your Sure account.

An authorized client can read the user and family financial data exposed by Sure’s MCP tools. Depending on the tools available in your Sure version, it may also be able to make changes. For example, import_bank_statement can create a transaction import from an uploaded bank-statement PDF. Only connect clients and AI providers you trust, and review tool requests before approving them.

Connect an AI assistant

Sign in to Sure and open Settings > MCP Server.
Copy the MCP server URL shown on the page. Sure builds this URL from your configured base URL and appends /mcp.
Open Claude.ai and go to Settings > Connectors.
Select Add a connector.
Enter the connector name and paste the MCP server URL from Sure Settings > MCP Server, then select Add.
Select the connector’s Connect button to complete authorization. Your browser redirects to Sure. Sign in if needed, then authorize access.

After authorization, the client can use the Sure tools exposed to it. Other MCP-compatible clients follow the same general process: give the client the URL from Settings > MCP Server, then complete Sure’s sign-in and authorization flow in your browser. The client handles the MCP and OAuth protocol details; you do not need to register it or create an access token manually.

Manage connected clients

The Connected clients section under Settings > MCP Server lists clients with active access to your account. Select Revoke beside a client to invalidate its token. Revoke clients you no longer use or recognize.

Available tools and access

The current Assistant.function_classes registry exposes the following tools. Tool availability and schemas can vary by Sure version, so clients should use tools/list as the source of truth for their installation.

Read

Tool	Description
`get_transactions`	Search transactions with optional filters and pagination; useful for finding transactions and calculating statistics for small groups of results
`get_recurring_transactions`	Detected and manual recurring transactions (subscriptions, bills, salaries) with expected dates and per-currency totals
`get_accounts`	List accounts with current and historical balances and account metadata
`get_holdings`	Search Investment and Crypto account holdings, including portfolio, performance, and cost-basis data; results are paginated
`get_balance_sheet`	Retrieve balance-sheet and net-worth data with historical information
`get_income_statement`	Retrieve income and expenses by category for a date range
`get_budget`	Compare a monthly budget with spending by category, with an optional prior-month trend comparison
`get_merchants`	List merchants with the IDs that `update_transaction` accepts and the exact names that `get_transactions` filters on
`get_tags`	List family tags alphabetically
`get_categories`	List family categories hierarchically, including IDs and parent relationships
`search_family_files`	Search uploaded family documents and return relevant excerpts and source filenames. This is the vector-store document index, not the Statement Vault — statements archived via `upload_account_statement` are not searchable through it

Create, update, and import

Tool	Description
`import_bank_statement`	Use AI extraction to import transactions from an already-uploaded bank-statement PDF; creates a transaction import and returns its ID and rows for review
`create_goal`	Create a savings goal linked to at least one eligible depository account, only after confirming key details with the user. The available-accounts list returned on failure includes how much each account has free to earmark and whether it is already claimed in full by another goal. Pass an `earmarks` map (account name → amount) to reserve a specific portion of an account rather than its whole balance — required when an account is already claimed in full.
`create_tag`	Create a unique family tag
`update_tag`	Update an existing tag’s name or color
`create_category`	Create a unique category, optionally as a subcategory
`update_category`	Update an existing category’s name, color, or icon
`update_transaction`	Update an existing transaction’s name, notes, category, merchant, or tags after finding it with `get_transactions`
`update_budget`	Update budget allocations for a month

import_bank_statement is not read-only. It requires a bank-statement PDF already uploaded to Sure and creates an import for review; it does not publish the import automatically. Because MCP access is scoped to the Sure user who authorizes the client, tools can access that user’s family data. Review tool calls whenever your client offers that option.

Preview tools

These tools appear only when the MCP user has opted into preview features under Settings > Preferences. Until then they are absent from tools/list, and calling one by name returns an “Unknown tool” error. The Statement Vault tools also require the user to be an admin or member, matching the permissions enforced in the web UI.

Tool	Description
`upload_account_statement`	Store a statement document (PDF/CSV/XLSX) in the Statement Vault; deduplicates by SHA-256
`list_account_statements`	List vault documents with their SHA-256, period, linked account, and review status
`get_account_statement`	One statement’s details and its reconciliation checks against the ledger. Present only after the opening and closing balances have been entered in the web UI. Does not return the file; stored documents are served only to a signed-in browser session
`get_statement_coverage`	Month-by-month statement coverage for an account: `covered`, `missing`, `mismatched`, `ambiguous`, `duplicate`, `not_expected`, each with a reconciliation status
`record_valuation`	Record an account’s value on a date, with a required source citation
`get_valuations`	List recorded valuations newest first, including the citation stored in each entry’s notes; the read pair for `record_valuation`
`get_insights`	Read the proactive insights feed (spending anomalies, cash-flow warnings, subscription audits, and more) without marking anything read

These tools are designed for agents that maintain a document-backed record of a family’s wealth over time.

Technical details

Sure serves MCP over JSON-RPC 2.0 at the URL displayed in Settings > MCP Server. The endpoint supports initialize, tools/list, and tools/call over HTTP POST requests. MCP-compatible clients use this URL and handle browser-based sign-in and authorization with Sure. Sure authenticates each MCP request with an active OAuth access token that has the read_write scope. The token’s resource owner determines the Sure user and family available to the tools. Sure creates a fresh transient session for that user for the request so an existing browser or impersonation session is not reused.

Protocol version and transport

Sure supports protocol versions 2025-03-26 and 2025-06-18. The current default is 2025-06-18, which introduces the Streamable HTTP transport used by clients such as Bifrost v1.6.3 and later. During the initialize handshake, the client sends its preferred version in params.protocolVersion. Sure selects that version if it is supported, or falls back to 2025-06-18 otherwise. The agreed version is returned in the initialize response body and echoed in the Mcp-Protocol-Version response header on every subsequent response. The initialize response also includes a sessionId field. Sure records the session in a server-side cache for 24 hours. Subsequent requests may include this value in the Mcp-Session-Id request header; Sure validates the session and echoes the ID in the corresponding response header. Clients that do not send a session ID are still served normally.

Legacy environment-token fallback

Self-hosted deployments can optionally support older clients that cannot complete the browser authorization flow. Set both MCP_API_TOKEN to a high-entropy secret and MCP_USER_EMAIL to an existing Sure user’s email. The client sends the configured token as a bearer token, and the selected user’s family data is exposed to the available MCP tools. This is a compatibility fallback: Sure tries OAuth access-token authentication first. Prefer the connection flow in Settings > MCP Server, and protect, rotate, and avoid logging any fallback token.

Optional Pipelock proxy

Pipelock is an optional security proxy that can scan MCP tool calls and responses for secret exfiltration, prompt injection, and tool poisoning before forwarding traffic to Sure. Sure’s AI Docker Compose example exposes Pipelock’s MCP listener on port 8889 and forwards it to Sure’s internal /mcp endpoint. The Helm chart can similarly expose a Pipelock MCP ingress. Operators who deploy it should provide users with the proxied MCP address. Pipelock adds scanning; it does not replace Sure’s browser sign-in and authorization or require users to configure OAuth manually. Operators can see the Pipelock section in the Helm guide for deployment and policy options. Use TLS, restrict direct access to /mcp when practical, and ensure clients use the proxied URL so they cannot bypass scanning.

Getting started

Key concepts

App features

Development

Authentication

Third party providers

Knowledge Base

Connect an AI assistant

Manage connected clients

Available tools and access

Read

Create, update, and import

Preview tools

Technical details

Protocol version and transport

Legacy environment-token fallback

Optional Pipelock proxy

​Connect an AI assistant

​Manage connected clients

​Available tools and access

​Read

​Create, update, and import

​Preview tools

​Technical details

​Protocol version and transport

​Legacy environment-token fallback

​Optional Pipelock proxy

Connect an AI assistant

Manage connected clients

Available tools and access

Read

Create, update, and import

Preview tools

Technical details

Protocol version and transport

Legacy environment-token fallback

Optional Pipelock proxy