Finance and revenue

The Mercury connector.

Account balances and transactions (read-only). Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.

How access is governed

5

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Mercury exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Mercury defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Mercury tool

5 tools, named as the agent sees them.

  • list_accountsread

    List the Mercury bank accounts on this workspace with current and available balances. Start here: every transaction tool needs an `id` from this list.

  • get_accountread

    Get one Mercury account by id: balances, status, and account metadata. Use the id from list_accounts.

  • list_transactionsread

    List transactions on one account, newest first by default. Pass start/end to scope a period — this list is long, so always bound it by date or keep the limit low. Each row carries an `id` for get_transaction.

  • get_transactionread

    Get one transaction in full, including routing/counterparty detail, attachments, currency-exchange info, and failure reason. Needs both the account_id and the transaction id from list_transactions.

  • list_recipientsread

    List the saved payment recipients on this Mercury workspace, to resolve a counterparty name seen on a transaction back to a known vendor. Read-only: this looks recipients up, it cannot create one or pay one.

Use it from any agent

The same Mercury tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Mercury API Token in your Mercury account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

More in finance and revenue

StripeChartMogulCartaRampPaddle

Connect Mercury once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.

Book a callSign in