MCP Worldpay runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 27 Sep 2026.
MCP server for Access Worldpay — enterprise processor: authorize, capture, refund, tokenize
Nothing serious here today
Today is the operative word: we check MCP Worldpay every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-worldpay -e 'WORLDPAY_USERNAME=<WORLDPAY_USERNAME>' -e 'WORLDPAY_PASSWORD=<WORLDPAY_PASSWORD>' -e 'WORLDPAY_ENTITY=<WORLDPAY_ENTITY>' -- npx -y @codespar/mcp-worldpay{
"mcpServers": {
"mcp-worldpay": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-worldpay"
],
"env": {
"WORLDPAY_ENTITY": "<WORLDPAY_ENTITY>",
"WORLDPAY_PASSWORD": "<WORLDPAY_PASSWORD>",
"WORLDPAY_USERNAME": "<WORLDPAY_USERNAME>"
}
}
}
}[mcp_servers.mcp-worldpay]
command = "npx"
args = ["-y", "@codespar/mcp-worldpay"]
env = { WORLDPAY_USERNAME = "<WORLDPAY_USERNAME>", WORLDPAY_PASSWORD = "<WORLDPAY_PASSWORD>", WORLDPAY_ENTITY = "<WORLDPAY_ENTITY>" }{
"mcpServers": {
"mcp-worldpay": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-worldpay"
],
"env": {
"WORLDPAY_ENTITY": "<WORLDPAY_ENTITY>",
"WORLDPAY_PASSWORD": "<WORLDPAY_PASSWORD>",
"WORLDPAY_USERNAME": "<WORLDPAY_USERNAME>"
}
}
}
}{
"servers": {
"mcp-worldpay": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@codespar/mcp-worldpay"
],
"env": {
"WORLDPAY_ENTITY": "<WORLDPAY_ENTITY>",
"WORLDPAY_PASSWORD": "<WORLDPAY_PASSWORD>",
"WORLDPAY_USERNAME": "<WORLDPAY_USERNAME>"
}
}
}
}Put your own values in place of
<WORLDPAY_USERNAME> (Access Worldpay API username (Basic Auth)), <WORLDPAY_PASSWORD> (Access Worldpay API password (Basic Auth)), <WORLDPAY_ENTITY> (Merchant entity identifier assigned during onboarding. Injected as merchant.entity into every request body).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
WORLDPAY_ENV (sandbox | production. Defaults to sandbox. sandbox -> https://try.access.worldpay.com, production -> https://access.worldpay.com), WORLDPAY_API_VERSION (Payments API version for the Content-Type/Accept media-type header. Defaults to v7).
Alternatives to MCP Worldpay
same job, measured the same wayMCP server for Izipay — Peru enterprise acquirer (Niubiz): authorize/capture/refund, cuotas
MCP server for Rede — Itaú-owned BR acquirer: authorize/capture/refund, zero-auth, card tokens
MCP server for Niubiz — Peru card acquirer: security token, session, authorize, reverse
Payway (ex-Decidir) — Argentina card acquiring: tokenize, charge, capture, refund
Read-only MCP server for 1C:Enterprise via OData with metadata and query builder tools.
Read-only financial reports for projects the authenticated FIMA user is authorized to access.
A Model Context Protocol (MCP) server for process management.
MCP server for Braintree (PayPal) — global card processing via GraphQL: charge, refund, vault
MCP Worldpay — questions
Answers built from our own checks of this server.