Mercury Invoicing Mcp
mercury-invoicing-mcp
Mercury Banking MCP server with full Invoicing API support — first MCP to expose Mercury's accounts receivable endpoints. A Model Context Protocol (MCP) server giving AI assistants (Claude, Cursor, Continue, etc.) full programmatic access to your Mercury business banking account, including the Invoicing API (one-shot + recurring) which is missing from every other Mercury MCP.
Features
- 34 tools across Banking (accounts, transactions, recipients, statements), Treasury, Invoicing (AR), Customers (AR), and Webhooks.
- Internal transfers between your own Mercury accounts.
- Recurring invoices + invoice attachments.
- Webhooks full CRUD (incl. update_webhook).
- Built-in safeguards: dual-window rate limit (daily + monthly), dry-run mode, redacted audit log.
- Sandbox auto-detect — tokens starting with
mercury_sandbox_automatically point atapi-sandbox.mercury.com.
Installation
npm install -g mercury-invoicing-mcp
Or directly via npx:
npx mercury-invoicing-mcp
Configuration
The server reads MERCURY_API_KEY from the environment. Get your API key at Mercury Settings → API Tokens.
{
"mcpServers": {
"mercury-invoicing": {
"command": "npx",
"args": ["-y", "mercury-invoicing-mcp"],
"env": {
"MERCURY_API_KEY": "secret-token:mercury_production_xxxxxxxxxxxxxxxx"
}
}
}
}
Safety
Outbound payments depend on YOUR Mercury approval policy. The MCP can only ever create the API call; what Mercury does with it is up to your workspace configuration. Set a strict approval policy in Mercury (e.g. require approval for any outbound payment, regardless of amount) if you intend to expose write tools to an agent.
License
MIT
Server Config
{
"mcpServers": {
"mercury-invoicing": {
"command": "npx",
"args": [
"-y",
"mercury-invoicing-mcp"
],
"env": {
"MERCURY_API_KEY": "secret-token:mercury_production_xxxxxxxxxxxxxxxx"
}
}
}
}