Nexi XPay

Provides an MCP interface to query Nexi XPay orders, transactions, warnings, and payment methods from a merchant account.
  • typescript

0

GitHub Stars

typescript

Language

3 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "stucchi-nexi-xpay-mcp-server": {
      "command": "uv",
      "args": [
        "run",
        "nexi-xpay-mcp-server"
      ],
      "env": {
        "NEXI_TEST": "false",
        "NEXI_ALIAS": "acme_merchant",
        "NEXI_SECRET_KEY": "your_secret_key"
      }
    }
  }
}

You can use this MCP server to enable AI assistants to securely query your Nexi XPay Back Office data, including orders, transaction details, warnings, and available payment methods from your merchant account. It provides a local, programmable bridge you can run with your MCP client to access Nexi XPay data in conversational flows or automation tasks.

How to use

Configure your MCP client to connect to a local MCP server that you run with the provided command. You will supply your merchant credentials in environment variables, then launch the server and point your MCP client at the local runtime. You can run one server per merchant by using distinct credentials.

How to install

Prerequisites you need before installation:

Install and run the MCP server using the runtime helper. Run the following command in your terminal.

uvx nexi-xpay-mcp-server

Configuration and usage notes

You configure the MCP server in your MCP client’s configuration file. The examples show how to register the server so your client can invoke the available tools.

Example configuration for a single merchant is shown here. Replace the placeholders with your actual alias and secret key.

{
  "mcpServers": {
    "nexi": {
      "command": "uvx",
      "args": ["nexi-xpay-mcp-server"],
      "env": {
        "NEXI_ALIAS": "your_alias",
        "NEXI_SECRET_KEY": "your_secret_key"
      }
    }
  }
}

Multiple merchants

If you need to manage more than one Nexi XPay merchant, run a separate MCP server instance for each merchant by using distinct credentials. Each instance is configured independently in your MCP client.

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

Available tools

list_orders

List orders with filters such as date range, channel, status, and transaction code.

order_details

Fetch full details of a specific transaction.

warnings

Retrieve warnings or anomalies. Defaults to the last 7 days if not specified.

payment_methods

List active payment methods for the merchant.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational