MCP Gateway · Claude Cowork
Connect Mercury to Claude Cowork
Month-end work in Mercury spans statements, transactions, invoices and Books, and it takes more than one question to get through it. Cowork can run those steps as one longer task and hand back a finished pack. The Mercury server reaches Cowork through the synced plugin marketplace, and agent hooks check each prompt with Speakeasy before a step runs.
- Category
- Sales & CRM
- Tools
- 34
- Authentication
- OAuth
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Mercury server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Mercury from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Mercury
Assemble a month-end close pack
Cowork gathers the month's statements for every operating and treasury account, lists the transactions behind them, and builds one document finance can review in order.
Reconcile Books against the bank
Cowork compares Books journal entries for the month with Mercury transactions and lists the entries that have no matching transaction, or the other way around.
Review card and credit usage
For a quarterly spend review, Cowork reads every credit account and the cards on each operating account, then summarizes the cards and credit lines finance should review.
Tools
34 tools
Each Mercury tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
How are Cowork sessions that use Mercury attributed?
Can finance use Mercury in Cowork from personal Claude accounts?
How do Claude Cowork users get Mercury?
Are Mercury calls from Claude Cowork logged?
Connect more