nexi-xpay-mcp-server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@nexi-xpay-mcp-server List the orders placed today"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
nexi-xpay-mcp-server
MCP server for the Nexi XPay Back Office APIs. Enables AI assistants (Claude, Cursor, etc.) to query orders, transaction details, warnings/anomalies, and payment methods from your Nexi XPay merchant account.
Tools
Tool | Description |
| List orders with filters (date range, channel, status, transaction code) |
| Full details of a specific transaction |
| Retrieve warnings/anomalies (default: last 7 days) |
| List active payment methods for the merchant |
Related MCP server: Qonto MCP Server
Prerequisites
Python >= 3.10
A Nexi XPay merchant account with Back Office API access
API credentials: Alias, API Key and Secret Key (from Nexi Back Office)
Installation
uvx nexi-xpay-mcp-serverUsage in .mcp.json
Add to your MCP configuration file (.mcp.json for Claude Code, claude_desktop_config.json for Claude Desktop):
{
"mcpServers": {
"nexi": {
"command": "uvx",
"args": ["nexi-xpay-mcp-server"],
"env": {
"NEXI_ALIAS": "your_alias",
"NEXI_SECRET_KEY": "your_secret_key"
}
}
}
}Multiple merchants
Use different keys to run one instance per merchant:
{
"mcpServers": {
"nexi-acme": {
"command": "uvx",
"args": ["nexi-xpay-mcp-server"],
"env": {
"NEXI_ALIAS": "acme_merchant",
"NEXI_SECRET_KEY": "acme_secret_key"
}
},
"nexi-globex": {
"command": "uvx",
"args": ["nexi-xpay-mcp-server"],
"env": {
"NEXI_ALIAS": "globex_merchant",
"NEXI_SECRET_KEY": "globex_secret_key"
}
}
}
}Environment variables
Variable | Required | Default | Description |
| Yes | — | Merchant alias (also used as API key) |
| Yes | — | Secret key for MAC calculation |
| No |
| Set to |
Development
git clone https://github.com/stucchi/nexi-xpay-mcp-server.git
cd nexi-xpay-mcp-server
uv syncLocal run:
NEXI_ALIAS=your_alias NEXI_SECRET_KEY=your_secret uv run nexi-xpay-mcp-serverLicense
MIT
Available Tools
4 toolslist_ordersA
Retrieve the list of orders from Nexi XPay Back Office. Supports filters by period, channel, status, and transaction code.
Inputs: periodo (required), canale, codiceTransazione, stato. Returns: result
order_detailsB
Retrieve full details of a specific order from Nexi XPay Back Office by transaction code.
Inputs: codiceTransazione (required). Returns: result
payment_methodsC
Retrieve active payment methods for a merchant from Nexi XPay Back Office.
Inputs: platform, platformVers, pluginVers. Returns: result
warningsA
Retrieve warnings/anomalies from Nexi XPay Back Office. Can filter by transaction code or date range.
Inputs: codiceTransazione, dataTransazioneDal, dataTransazioneAl. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect your AI assistant to NexPay to view payments, contacts, commissions, and exchange rates.
Connect AI to store orders, products and inventory with scoped access and human approvals.
Manage GoCardless payments, mandates, subscriptions, refunds and payouts via AI assistants.
Enables AI assistants to retrieve event data and execute event management operations in Nunify.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.24 npm1MIT

Qonto MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Qonto financial data including organization info, account balances, transaction history, and business operations through natural language.42MIT- AlicenseAqualityDmaintenanceEnables AI agents to operate Xental merchant accounts via natural language, provisioning virtual accounts, monitoring transactions, and executing payouts.13MIT
- FlicenseNot gradedqualityBmaintenanceEnables secure, bilingual AI assistants to query and manage payments, orders, refunds, transactions, wallets, fraud risk, and statistics with per-user data isolation enforced on every tool call.-