Mercury Invoicing Mcp
About
Mercury Banking MCP server with full Invoicing API support — first MCP to expose Mercury's accounts receivable endpoints. 34 tools covering banking, treasury, recipients, internal transfers, customers, recurring invoices, and webhooks. Built-in safeguards: dual-window rate limiti
Details
- Author
- klodr
- Downloads
- 293
- Categories
- Other
Jump to
- 34 tools across Banking, Treasury, Invoicing, Customers, and Webhooks.
- Internal transfers between owned Mercury accounts.
- Recurring invoices and invoice attachments.
- Webhooks full CRUD, including update_webhook.
- Built-in safeguards: dual-window rate limit, dry-run mode, redacted audit log.
- Sandbox auto-detection for tokens starting with mercury_sandbox_.
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Mercury Invoicing McpCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install globally with npm install -g mercury-invoicing-mcp or run via npx mercury-invoicing-mcp. Set the MERCURY_API_KEY environment variable with a Mercury API token obtained from Mercury Settings → API Tokens. Configure the server in your MCP client’s mcpServers block with the command, arguments, and environment variable.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mercury invoicing mcp": {
"mercury-invoicing": {
"command": "npx",
"args": [
"-y",
"mercury-invoicing-mcp"
],
"env": {
"MERCURY_API_KEY": "secret-token:mercury_production_xxxxxxxxxxxxxxxx"
}
}
}
}
}McpServers
{
"mercury-invoicing": {
"command": "npx",
"args": [
"-y",
"mercury-invoicing-mcp"
],
"env": {
"MERCURY_API_KEY": "secret-token:mercury_production_xxxxxxxxxxxxxxxx"
}
}
}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 withmercury_sandbox_ automatically point at api-sandbox.mercury.com.
Installation
``bash
npm install -g mercury-invoicing-mcp
`
Or directly via npx:
`bash
npx mercury-invoicing-mcp
`
Configuration
The server reads MERCURY_API_KEY from the environment. Get your API key at Mercury Settings → API Tokens.
`json
{
"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
MITSign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
