Skip to main content
Glama
Sherman-Studio

revolut-merchant-mcp

by Sherman-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to revolut-merchant-mcp

No user-submitted related servers found.

    Related Servers

    • clover-mcp

      SBolivarLoL
      A
      license
      A
      quality
      A
      maintenance
      MCP server for the Clover POS REST API that gives AI assistants read and safe-write access to a merchant's sales, inventory, orders, and customers.
      56
      MIT

    • adaptis-mcp-server

      fredericktvf
      F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI agents interact with the Adaptis (MEG) payment gateway, enabling payment link creation, transaction queries, refunds, and integration helpers like generating signed forms and verifying callbacks.
      -

    • invoiceninja-mcp

      ambaloo
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.
      32
      16 npm
      2
      MIT

    • Recharge Storefront API MCP

      bearded-giant
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server that provides complete access to the Recharge Storefront API endpoints. Enables AI assistants to manage subscriptions, customers, orders, and billing through a standardized interface.
      2
      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

    B3.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource (customer, order, plan, subscription) and a distinct action (get single vs list multiple). There is no overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: get_<resource> for single retrieval and list_<resource> for listing. No mixing of conventions.

    Tool Count5/5

    With 8 tools covering retrieval of four core merchant entities, the count is well-scoped and appropriate for a focused read-only interface.

    Completeness2/5

    The tool set lacks any mutation operations (create, update, delete), which are essential for a complete merchant workflow. Agents cannot create orders, subscriptions, or manage customers.

    Maintenance

    ActivityStale
    ResponsivenessSyncing

    Resources