revolut-merchant-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REVOLUT_SANDBOX | No | false = production (guarded) | true |
| REVOLUT_API_VERSION | No | Sent as Revolut-Api-Version | 2024-09-01 |
| REVOLUT_MCP_ALLOW_WRITES | No | Register the create/cancel tools | false |
| REVOLUT_MERCHANT_SECRET_KEY | Yes | Merchant API secret (sandbox or live) | |
| REVOLUT_I_UNDERSTAND_PRODUCTION | No | Required to run against production | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_customersB | List Merchant customers, optionally filtered by exact email address. |
| get_customerC | Retrieve a single Merchant customer by its id. |
| list_ordersC | List recent Merchant orders. |
| get_orderB | Retrieve a single Merchant order by its id. |
| list_subscriptionsC | List subscriptions, optionally filtered by customer id. |
| get_subscriptionC | Retrieve a single subscription by its id. |
| list_plansB | List Merchant subscription plans. |
| get_planA | Retrieve a single plan, including its variations, by id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
All tools follow a consistent verb_noun pattern: get_<resource> for single retrieval and list_<resource> for listing. No mixing of conventions.
With 8 tools covering retrieval of four core merchant entities, the count is well-scoped and appropriate for a focused read-only interface.
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.