Query and manage Mercoa AP/AR bill-pay: entities, invoices, transactions and payment methods. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"mercoa": {
"url": "https://mercoa.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"mercoa": {
"type": "http",
"url": "https://mercoa.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Mercoa API key.
Find it in your Mercoa dashboard under API keys. Your key is used only to call the API on your behalf and to derive a private account id; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mercoa API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Mercoa connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
mercoa_find_entities | read | Find entities Find/search entities (buyers, vendors, payors, payees). Use to look up counterparties by name/email/foreignId or list all. GET /entity. |
mercoa_get_entity | read | Get entity Get a single entity by ID (or foreign ID). GET /entity/{entityId}. |
mercoa_get_entity_events | read | Get entity events Get the event/audit log for an entity. GET /entity/{entityId}/events. |
mercoa_get_entity_invoice_metrics | read | Get entity invoice metrics Get aggregate invoice metrics (totals/counts, grouped by currency) for an entity's payables/receivables — for AP/AR dashboards and aging. GET /entity/{entityId}/invoice-metrics. |
mercoa_list_entity_payment_methods | read | List entity payment methods List an entity's payment methods (bank accounts, cards, check, etc.). GET /entity/{entityId}/paymentMethods. |
mercoa_get_payment_method | read | Get payment method Get a single payment method for an entity. GET /entity/{entityId}/paymentMethod/{paymentMethodId}. |
mercoa_list_entity_users | read | List entity users List the users belonging to an entity (approvers, admins, etc.). GET /entity/{entityId}/users. |
mercoa_find_invoices | read | Find invoices Find/search invoices (bills) across payers and vendors. Filter by status, entity, date, approver and more. GET /invoices (plural list endpoint). |
mercoa_get_invoice | read | Get invoice Get a single invoice (bill) by ID. GET /invoice/{invoiceId}. |
mercoa_get_invoice_events | read | Get invoice events Get the event/audit log for an invoice (status changes, approvals, payments). GET /invoice/{invoiceId}/events. |
mercoa_find_transactions | read | Find transactions List/search payment transactions. Filter by entity, invoice, status, type and date. GET /transactions. |
mercoa_get_transaction | read | Get transaction Get a single payment transaction by ID. GET /transaction/{transactionId}. |
mercoa_get_organization | read | Get organization Get the caller's Mercoa organization configuration (settings, payment methods enabled, etc.). GET /organization. |
mercoa_create_entity | write | Create entity WRITE — creates a real entity (customer/vendor/payor/payee) in Mercoa. Supply role flags, accountType, and a nested `profile` object (business or individual details). POST /entity. |
mercoa_create_invoice | write | Create invoice WRITE — creates a real invoice/bill in Mercoa. Set status (DRAFT to stage, NEW to submit), amount, currency, payer/vendor, dates and line items. POST /invoice. |
mercoa_update_invoice | write | Update invoice WRITE — updates an existing invoice/bill (all fields optional). Commonly used to advance status (e.g. DRAFT→NEW→SCHEDULED) or change amounts, dates, or payment methods. POST /invoice/{invoiceId}. |
mercoa_add_invoice_comment | write | Add invoice comment WRITE — adds a comment to an invoice (visible in its activity log). POST /invoice/{invoiceId}/comment. |
mercoa_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
mercoa_request_feature | Request a missing feature Tell usefulapi that the user needs something the Mercoa tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
mercoa_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Mercoa tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
mercoa_cancel_subscription | Cancel the Pro subscription Cancel the caller's Mercoa Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run mercoa_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this Mercoa server only. Subscribe with mercoa_upgrade (it returns a Stripe Checkout link). Cancel any time with mercoa_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running mercoa_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Mercoa. The server calls the Mercoa API with your own Mercoa access, so it sees only the data that your account can see.
The login page asks for your Mercoa API key. See Before you connect for where to find it.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Mercoa API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Mercoa API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Mercoa.
Yes, if you approve it. 4 of the 17 Mercoa tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Mercoa server only. Run mercoa_usage_status to see how many calls you used.
Ask the AI to run mercoa_upgrade: it returns a Stripe Checkout link. To cancel, run mercoa_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with mercoa_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.