Skip to main content
Glama
SqREL

monobank-mcp

by SqREL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to monobank-mcp

No user-submitted related servers found.

    Related Servers

    • Monobank MCP Server

      akutishevsky
      A
      license
      A
      quality
      A
      maintenance
      Enables integration with Monobank API to check currency exchange rates, view account balances, and retrieve transaction statements through natural language queries.
      3
      31 npm
      10
      MIT

    • Monobank MCP Server

      nklymok
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Monobank personal account data through MCP tools, allowing users to fetch client info, accounts, and jars. It also enables retrieving account statements for specific time periods.
      -

    • Mono-MCP

      clar1k
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to retrieve and format Monobank account statements and transactions by date range.
      7 npm
      4
      MIT

    • monzo-mcp

      Matthew7727
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Monzo bank accounts, including checking balances, listing transactions, and managing pots through natural language via the MCP protocol.
      9
      25 npm
      MIT

    • Pekao MCP Server

      xnetcat
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Pekao banking API for account information, payment initiation, and confirmation of funds via MCP tools.
      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 5 tools

    Disambiguation5/5

    Each tool targets a distinct concern: public rates, public key verification, client account data, webhook configuration, and transaction statements. There is no overlap or ambiguity between their purposes.

    Naming Consistency5/5

    All read-oriented tools follow the consistent get_<resource> pattern, and the single mutating tool uses the equally clear set_webhook. The naming is predictable and immediately conveys the action and target.

    Tool Count5/5

    Five tools is an appropriate, well-scoped surface for a Monobank integration. Each tool maps to a core API capability without unnecessary duplication or bloat.

    Completeness5/5

    The toolset covers the essential Monobank operations: rates, client info, statements, webhook setup, and the public key needed for webhook verification. There are no obvious dead ends or missing domain-critical operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources