Skip to main content
Glama
klodr

mercury-invoicing-mcp

by klodr
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

Related Servers

Alternatives to mercury-invoicing-mcp

  • faxdrop-mcp

    klodr
    A
    license
    A
    quality
    A
    maintenance
    Enables AI assistants to send real faxes through the FaxDrop API. Provides safeguards including rate limiting, dry-run mode, and audit logging for secure fax operations.
    3
    9 npm
    5
    MIT

Related Servers

  • Mercury Multiorg MCP

    dkaleganov
    A
    license
    A
    quality
    A
    maintenance
    An unofficial, read-only MCP server for Mercury business banking. It holds one read-only API token per organization, so a single AI session can work across several Mercury organizations; Mercury's own connector binds one organization per connection.
    24
    MIT

  • Mercury MCP

    dragonkhoi
    A
    license
    Not graded
    quality
    D
    maintenance
    Simple MCP server that interfaces with the Mercury API, allowing you to talk to your Mercury banking data from any MCP client like Cursor or Claude Desktop.
    4
    MIT

  • Mercury MCP Server

    Fyko
    A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for Mercury Banking API that enables listing accounts and retrieving transactions via natural language.
    5 npm
    MIT

  • Mercury Enhanced MCP

    collinsb1
    A
    license
    A
    quality
    D
    maintenance
    A custom MCP server for the Mercury banking API that uses personal API tokens to avoid session expiry. It provides 15 tools for managing accounts, transactions, recipients, treasury, and more.
    15
    MIT
  • Xero MCP Server by XeroAPI

    Xero MCP Serverofficial

    XeroAPI
    A
    license
    B
    quality
    F
    maintenance
    A Model Context Protocol server implementation providing standardized access to Xero's accounting and business features, enabling operations like contact management, invoice creation, and chart of accounts management through MCP.
    51
    8,373 npm
    365
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 36 tools

Disambiguation4/5

Tools are mostly distinct by resource type (accounts, transactions, recipients, invoices, customers, webhooks), and descriptions explicitly cross-reference alternatives (e.g., deposit vs. credit vs. treasury). Minor confusion possible between mercury_list_transactions and mercury_list_credit_transactions, but the descriptions clearly delineate the surfaces.

Naming Consistency5/5

All tools follow a consistent mercury_<verb>_<noun> pattern with clear verbs (list, get, create, update, delete, cancel, send, add). The naming convention is uniform across all 36 tools, making the set highly predictable.

Tool Count3/5

36 tools is on the heavy side, but the server covers multiple distinct Mercury surfaces (deposit accounts, credit, treasury, payments, AR invoicing, webhooks). Each tool maps to a real API endpoint, so the count is justified, though it approaches the upper bound of what an agent can easily navigate.

Completeness4/5

The tool set covers core CRUD/lifecycle for accounts, transactions, recipients, invoices, customers, and webhooks. Notable gaps: no card creation/freezing, no invoice attachment upload, no credit-account statement access, and no webhook delivery history — but these are explicitly documented as API limitations, and the core workflows (send money, invoice, manage webhooks) are complete.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources