Skip to main content
Glama
dkaleganov

Mercury Multiorg MCP

by dkaleganov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Mercury Multiorg MCP

No user-submitted related servers found.

    Related Servers

    • 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.
      7 npm
      MIT

    • plaid-mcp

      kenchambers1987-png
      A
      license
      B
      quality
      C
      maintenance
      A read-only MCP server that lets AI clients query real financial data (bank, credit card, loan, brokerage) via Plaid or Teller, offering tools for balances, transactions, investments, liabilities, identity, income, and debt analysis.
      24
      MIT

    • financy

      open-finance-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes banking data (connections, accounts, balances, transactions) and agent skills, allowing AI agents to query and refresh financial data via stdio.
      44 npm
      6
      Apache 2.0
    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 24 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: list_accounts vs list_credit_accounts vs list_treasury are clearly separated by descriptions, as are list_transactions vs list_treasury_transactions and list_recipients vs list_customers. The get_* tools (get_org, get_card, get_invoice) are unambiguously for single-item retrieval of distinct resources. No two tools have overlapping purposes.

    Naming Consistency4/5

    The vast majority of tools follow the consistent verb_noun pattern: 20 list_* tools and 3 get_* tools. Two outliers (reportable_totals, server_info) are descriptive but don't follow the verb_noun convention, which is a minor deviation given the overall consistency.

    Tool Count4/5

    With 24 tools, this is on the high end but appropriate for a comprehensive read-only Mercury integration covering entities, accounts, transactions, recipients, tax docs, treasury, credit, cards, categories, merchants, customers, invoices, users, events, and webhooks. Each tool maps to a distinct resource, so the count is justified by the scope.

    Completeness4/5

    The surface is read-only but covers all major Mercury resources comprehensively: accounts, transactions, recipients, tax docs, org, statements, treasury, credit, cards, categories, merchants, customers, invoices, users, events, and webhooks. Minor gaps exist (e.g., no get_statement_pdf or get_invoice_pdf in the tool list despite mentions in descriptions), but core read workflows are fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources