Mercury MCP server for Claude, Codex and Cursor

What your AI apps can do with Mercury

Read accounts and balances
Search transactions

Mercury MCP tools

37 tools, taken from the publisher's documentation on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Tool	What it does
`requestSendMoney`	Create a payment request to an existing recipient; needs approval in Mercury
`requestTransferMoney`	Create a transfer request between your Mercury accounts; needs approval in Mercury
`createCategory`	Create a custom expense category immediately
`editCategory`	Update a custom expense category immediately
`updateTransaction`	Update or clear a transaction's note or category immediately
`getAccount`	Get details of a specific account by ID
`getAccountCards`	Get the debit and credit cards linked to an account
`getAccountStatements`	Get monthly statements for an account, filterable by date range
`getTransaction`	Get a specific transaction by account ID and transaction ID
`getAccounts`	List all Mercury accounts for the organization
`listCategories`	List the organization's custom expense categories
`listCredit`	List all credit accounts for the organization
`getOrganization`	Get organization information such as EIN, legal name and DBAs
`getRecipient`	Get a specific recipient by ID
`getRecipients`	List all recipients
`listTransactions`	List transactions with date, status and category filters
`getTreasury`	List all treasury accounts for the organization
`getTreasuryTransactions`	Get paginated transactions for a treasury account
`getCard`	Get a specific card by ID
`listCards`	List cards with pagination
`getUser`	Get a specific user by ID
`getUsers`	List all users in the organization
`getWebhook`	Get a specific webhook endpoint by ID
`getWebhooks`	List webhook endpoints, filterable by status
`getTransactionById`	Get a transaction by ID with attachments, check images and metadata
`listSendMoneyApprovalRequests`	List send money approval requests, filterable by account and status
`getSafeRequest`	Get a specific SAFE request by ID
`getSafeRequests`	List all SAFE requests for the organization
`listRecipientsAttachments`	List tax form attachments across all recipients
`getAttachment`	Get attachment details, including a download URL
`getCustomer`	Get a specific customer by ID
`listCustomers`	List customers with cursor pagination
`getInvoice`	Get an invoice by ID
`listInvoices`	List invoices with cursor pagination
`listInvoiceAttachments`	List attachments for a specific invoice
`listTransferMoneyApprovalRequests`	Check internal transfer requests
`getTransferMoneyApprovalRequest`	Check an internal transfer request

Suggested access for each AI app

The documentation this list comes from doesn't mark Mercury's tools as read-only or destructive. Read each tool's description and decide per app before allowing it.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Mercury connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

Connect once. Add Mercury to a workspace (browser sign-in). Toolstile keeps the credential, so no agent config holds it.
Choose access per app. Give Claude Code every Mercury tool, give Cursor only the read tools, or keep Mercury away from an app entirely.
Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Mercury MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Mercury in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Mercury endpoint to each app separately. In Claude Code:

Shell

claude mcp add --transport http mercury 'https://mcp.mercury.com/mcp'

In Cursor's mcp.json:

JSON

{
  "mcpServers": {
    "mercury": {
      "url": "https://mcp.mercury.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Mercury MCP documentation for what your client needs.

Before you connect

A Mercury account. Sign-in uses your Mercury permissions.

Server details

Detail	Value
Publisher	Mercury
Endpoint	`https://mcp.mercury.com/mcp`
Authentication	Browser sign-in
Categories	Data & infrastructure
Tool list	37 tools, observed 29 October 2026 (docs)

Mercury MCP documentation