nexi-xpay-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXI_TEST | No | Set to 'true' to use the test environment | false |
| NEXI_ALIAS | Yes | Merchant alias (also used as API key) | |
| NEXI_SECRET_KEY | Yes | Secret key for MAC calculation |
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_ordersA | Retrieve the list of orders from Nexi XPay Back Office. Supports filters by period, channel, status, and transaction code. |
| order_detailsB | Retrieve full details of a specific order from Nexi XPay Back Office by transaction code. |
| warningsA | Retrieve warnings/anomalies from Nexi XPay Back Office. Can filter by transaction code or date range. |
| payment_methodsC | Retrieve active payment methods for a merchant from Nexi XPay Back Office. |
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 4 tools
Each tool targets a distinct resource or aspect: orders list, order details, payment methods, and warnings. There is no overlap in purpose, making it easy for an agent to select the correct tool.
All tool names use snake_case, which is consistent. However, the pattern is not uniform: 'list_orders' follows verb_noun, while 'order_details', 'payment_methods', and 'warnings' are noun_noun or noun-only. This minor inconsistency prevents a perfect score.
With 4 tools, the server is scoped to a focused set of read operations. While slightly low, it covers the essential queries for the Nexi XPay Back Office without unnecessary bloat, making it appropriate for its purpose.
The tools cover the main read operations: listing orders, getting details, viewing payment methods, and checking warnings. Missing operations like creating or updating orders are not expected if the server is read-only, so the surface is largely complete for its intended use.