Skip to main content
Glama
klodr

mercury-invoicing-mcp

mercury_create_invoice

Create a new invoice for an existing customer, send it by email instantly, and get back the invoice ID, status, amount, and payment URL.

Instructions

Create a new invoice (one-shot or to be sent recurrently). Requires AR write scope.

USE WHEN: billing a customer that already exists in Mercury (customerId from mercury_create_customer or mercury_list_customers). Set sendEmailOption: "SendNow" to email the invoice immediately to the customer's contact email.

DO NOT USE: when the customer does not exist yet (call mercury_create_customer first). To attach a file to the invoice, use the Mercury web app at creation time — the API attachment-upload endpoint is not exposed by this MCP currently.

SIDE EFFECTS: writes a new invoice to Mercury. Persistent. With sendEmailOption: "SendNow" (the default), Mercury also sends a real email with a payment link to the customer — confirm the customer's email and the line items before calling. Mercury Plus tier required for the AR write scope.

RETURNS: { id, status, amount, paymentUrl, ... }paymentUrl is the Mercury-hosted page where the customer pays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesCustomer ID (created via mercury_create_customer)
destinationAccountIdYesMercury account ID where invoice payments will be deposited
invoiceDateYesInvoice date (YYYY-MM-DD)
dueDateYesDue date (YYYY-MM-DD)
lineItemsYesInvoice line items
achDebitEnabledNoAllow ACH debit payments. Default: true
creditCardEnabledNoAllow credit card payments. Default: true
useRealAccountNumberNoShow real (vs virtual) account number on the invoice. Default: false
ccEmailsNoCC emails for notifications
sendEmailOptionNoWhether to email the invoice immediately. Default: SendNow
invoiceNumberNoCustomer-facing invoice number (≤255 chars; Mercury rejects 300+ characters on the edit endpoint)
poNumberNoPurchase order number
payerMemoNoMemo shown to payer
internalNoteNoNote visible only to your org
servicePeriodStartDateNoService period start (YYYY-MM-DD)
servicePeriodEndDateNoService period end (YYYY-MM-DD)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description fully covers side effects: persistent write, email sent on default SendNow, and Mercury Plus tier requirement. Discloses important behavior beyond schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with labeled sections, front-loaded purpose. Slightly verbose but every sentence adds value given tool complexity. Could be tighter but effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers return value shape, side effects, prerequisites, and tier requirement. No output schema exists, so description compensates well. Complete for a complex 16-parameter creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with descriptions. Description adds minimal extra parameter detail (e.g., line item name length), but mostly provides contextual usage guidance rather than parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states 'Create a new invoice (one-shot or to be sent recurrently)' and requires 'AR write scope'. Clearly differentiates from sibling tools like update/cancel by focusing on creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear 'USE WHEN' vs 'DO NOT USE' sections, specifying prerequisites (customer must exist) and alternatives (mercury_create_customer). Also advises on sendEmailOption and attachment limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/klodr/mercury-invoicing-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server