MCP Gateway · Claude
Connect Mercury to Claude
Founders, operations leads and finance staff ask the same Mercury questions every week. Claude can answer them from live data: what the team spent on software last month, whether a customer's invoice went out, or the company's exact legal name. Each person reaches only the Mercury tools their role allows, and every call is logged.
- Category
- Sales & CRM
- Tools
- 34
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Mercury MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Mercury call inspected and logged.
Set up
Add Mercury to Claude in 4 steps
- 01
Add Mercury from the catalog
An admin finds Mercury in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Mercury uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Mercury
Give teams the
mcp:connectscope on the Mercury server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Mercury to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Mercury from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Mercury needs its own OAuth grant, so each person connects it once. Until they do, Mercury calls fail while the rest of the gateway keeps working.
From then on, Mercury's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Mercury
Answer what the team spent
Ask Claude what was spent in a category over a date range. It filters transactions by category and date and gives you a total and the largest items.
Check an invoice for a customer
Before replying to a customer about billing, ask Claude to find their invoice in Mercury and confirm its details and the customer record it was sent to.
Pull company details for a form
Vendor forms and bank questionnaires ask for the legal business name, EIN and DBAs. Claude reads them from Mercury so they're copied correctly.
Tools
34 tools
Each Mercury tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
getAccount
Get account by ID
getAccountCards
Retrieve all debit and credit cards associated with a specific account.
getAccountStatements
Retrieve a paginated list of monthly statements for a specific account. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters, as well as date range filtering with start and end parameters.
getTransaction
Get transaction by ID
getAccounts
Retrieve a paginated list of accounts. Supports cursor-based pagination with limit, order, start_after, and end_before query parameters.
getAttachment
Retrieve attachment details including download URL
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Mercury call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Mercury tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Mercury can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Do Mercury questions in Claude count toward Speakeasy budgets?
Can Claude conversations about Mercury be reviewed later?
How do Claude users get Mercury?
Are Mercury calls from Claude logged?
Connect more