Skip to main content
Glama
Sign In
mercury-invoicing-mcp

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
    255 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.
    4 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

    Xero MCP Serverofficial

    XeroAPI
    A
    license
    B
    quality
    D
    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
    15,341 npm
    389
    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.3/5.0

Scored across 39 tools

Disambiguation4/5

The tool set is generally well separated by resource surface: deposit accounts, IO Credit accounts, Treasury, recipients, customers, invoices, statements, and webhooks each have dedicated tools. The many list/get pairs and three statement variants could be confused, but the descriptions consistently clarify boundaries with DO NOT USE notes. A few similar tools (e.g. mercury_list_transactions vs mercury_list_credit_transactions vs mercury_list_treasury_transactions) require careful reading but are distinguishable.

Naming Consistency4/5

Almost all tools use a consistent mercury_ prefix and snake_case verb_noun pattern. Minor deviations exist, such as mercury_add_recipient vs mercury_create_customer and mercury_request_send_money, but these are still readable and predictable. No chaotic mixing of camelCase or vague verbs.

Tool Count2/5

Thirty-nine tools is heavy for the apparent scope, even for a broad Mercury banking/invoicing surface. The set covers many distinct resources, but the sheer number of list/get/create/update/cancel/delete variants makes discovery and selection costly. A more consolidated or grouped surface would likely be easier to use.

Completeness4/5

Core workflows are well covered: accounts, transactions, statements, customers, invoices, recipients, webhooks, cards, categories, Treasury, and payments. There are some notable gaps, such as no recipient delete, no invoice attachment upload, and limited card lifecycle operations, but most are explicitly documented as API or MCP limitations. Agents can work around the remaining gaps for typical invoicing and banking tasks.

Maintenance

ActivityMaintained
ResponsivenessSlow

Resources