Nexi XPay

io.github.stucchiPublished by GitHub account stucchiv1.2.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant query orders, transaction details, warnings and payment methods from a Nexi XPay merchant Back Office account.

What you can do
List orders with filters such as date range, channel, status and transaction code, and open the full details of a specific transaction. Retrieve warnings and anomalies, defaulting to the last seven days. List the active payment methods configured for the merchant.
When to use it
Useful when you work with a Nexi XPay merchant account and want to ask an assistant about recent orders, individual transactions, anomalies or enabled payment methods without opening the Back Office manually.
Requirements
Runs locally as a Python package (Python 3.10 or newer), typically launched with uvx. Needs a Nexi XPay merchant account with Back Office API access and the credentials NEXI_ALIAS and NEXI_SECRET_KEY set as environment variables; NEXI_TEST optionally switches to the test environment. Network access to the Nexi APIs is required.
Before you install
The server holds merchant API credentials: NEXI_ALIAS and NEXI_SECRET_KEY are passed in plain environment variables, so keep the configuration file private. Queries go to your live merchant data unless NEXI_TEST is set to true, so test against the test environment first. The listed tools read data; no write or payment actions are documented.

Installation

In SourceWeft

  1. Open Nexi XPay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

bash
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):

json
{  "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:

json
{  "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

bash
git clone https://github.com/stucchi/nexi-xpay-mcp-server.gitcd nexi-xpay-mcp-serveruv sync

Local run:

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

License

MIT

Source: README.md at commit ce23675

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts