English Français العربية

Nexi XPay

Official registry E-commerce

MCP server for Nexi XPay Back Office APIs: orders, transactions, warnings.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package nexi-xpay-mcp-server
Claude Code 
claude mcp add nexi-xpay -- uvx nexi-xpay-mcp-server==1.2.1
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "nexi-xpay": {
            "command": "uvx",
            "args": [
                "nexi-xpay-mcp-server==1.2.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. nexi-xpay-mcp-server
  2. Tools
  3. Prerequisites
  4. Installation
  5. Usage in .mcp.json
  6. Environment variables
  7. Development
  8. License

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

ToolDescription
list_ordersList orders with filters (date range, channel, status, transaction code)
order_detailsFull details of a specific transaction
warningsRetrieve warnings/anomalies (default: last 7 days)
payment_methodsList active payment methods for the merchant

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-server

Usage 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

VariableRequiredDefaultDescription
NEXI_ALIASYes—Merchant alias (also used as API key)
NEXI_SECRET_KEYYes—Secret key for MAC calculation
NEXI_TESTNofalseSet to true to use the test environment

Development

git clone https://github.com/stucchi/nexi-xpay-mcp-server.git
cd nexi-xpay-mcp-server
uv sync

Local run:

NEXI_ALIAS=your_alias NEXI_SECRET_KEY=your_secret uv run nexi-xpay-mcp-server

License

MIT

Frequently asked questions

What is Nexi XPay?

MCP server for Nexi XPay Back Office APIs: orders, transactions, warnings.

How do I install Nexi XPay?

It runs on your machine. In Claude Code: claude mcp add nexi-xpay -- uvx nexi-xpay-mcp-server==1.2.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Nexi XPay need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Nexi XPay open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Nexi XPay?

It is published by stucchi. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.