Skip to main content
Glama
jbctechsolutions

@jbctechsolutions/mcp-mercury

by jbctechsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @jbctechsolutions/mcp-mercury

No user-submitted related servers found.

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

    • Monarch Money MCP Server

      rmarji
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP and HTTP proxy server for accessing Monarch Money financial data, enabling transaction analysis, budget tracking, and cashflow insights through natural language.
      6
      MIT

    • finance-reconcile-mcp

      nalyDzzz
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for reconciling SimpleFIN bank data against Firefly III ledger, enabling audit and review workflows without mutation.
      19
      11 npm
      1
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource: accounts, transactions, or statements, with no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_accounts, get_transaction), making them predictable and easy to differentiate.

    Tool Count5/5

    Six tools cover the core banking operations (accounts, transactions, statements) without being too many or too few, fitting the server's read-only purpose.

    Completeness4/5

    The tool set covers listing and retrieving accounts, transactions, and statements, but lacks any write operations; however, the read-only design is intentional and well-scoped.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources