mcpField
N
Nexi XPay

Nexi XPay

Local
github.com/stucchiFinance0Updated 35w ago
Repository

About Nexi XPay

Nexi XPay is an MCP server for merchants and AI assistants to query Back Office data, including orders, transactions, warnings, and payment methods.

Key features

  1. 01Filter orders by date, channel, or status
  2. 02Retrieve transaction details
  3. 03Fetch warnings and anomalies
  4. 04List active payment methods
  5. 05Configure instances for multiple merchants

Use cases

  1. 01Review orders from a selected period
  2. 02Inspect transaction details
  3. 03Investigate recent payment anomalies
  4. 04Check a merchant’s active payment methods

MCP support

The server exposes Nexi XPay Back Office API tools to MCP clients for querying orders, transaction details, warnings, and payment methods.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "stucchi-nexi-xpay": {
      "command": "uvx",
      "args": [
        "nexi-xpay-mcp-server"
      ]
    }
  }
}
Run commanduvx nexi-xpay-mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypinexi-xpay-mcp-server1.2.1

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

nexi-xpay-mcp-server

MCP PyPI License: MIT

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.