What it does
The Nexi XPay MCP server exposes the Nexi XPay Back Office APIs through the Model Context Protocol, so an AI client can work with orders, transactions and warnings held in that payment back office. It is listed under development tools, and it is an MCP server rather than a skill or plugin.
It suits developers who want an AI assistant to query or manage payment records from Nexi XPay as part of a coding or operations workflow, instead of calling the Back Office APIs by hand. The publisher description does not list further use cases, so the scope is limited to the three areas named.
The source does not describe the setup steps. Running it presumably requires access to a Nexi XPay Back Office account and the credentials it needs; the publisher's documentation should be checked for the exact configuration.
Limitations and requirements
The source does not state installation or configuration steps. Access to Nexi XPay Back Office APIs is implied by the server's purpose, but the required credentials and account details are not specified.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
Nexi XPay
MCP server for Nexi XPay Back Office APIs: orders, transactions, warnings.
v1.2.1As shown on registry.modelcontextprotocol.io when we last read it