Worldpay MCP is an open-source Model Context Protocol server that exposes Worldpay's payment APIs as callable tools for AI agents — enabling any MCP-compatible agent to charge cards, verify tokens, follow up on transactions, and generate hosted payment links without writing custom integration code. Launched November 2025 and freely available on GitHub, it is one of the clearest examples of a major payment processor designing its API surface explicitly for LLM consumption.
What It Does
The server ships four tool definitions out of the box:
| Tool | What it does |
|---|---|
| Make Payment | Submits a direct charge to the Worldpay Payments API using a Checkout-generated Session URL |
| Verify Card / Generate Token | Runs a card verification and returns a reusable payment token via Worldpay Verified Tokens |
| Follow-on Actions | Executes next-action links returned by any payment response — settle, cancel, refund, etc. |
| Generate Payment Link | Creates a hosted payment page link that can be handed to a user to complete payment |
The follow-on action model is notable: Worldpay's API returns hypermedia links for each possible next step after a transaction, and the MCP server exposes a single generic tool that takes any such link and invokes it. This lets an agent chain together a full payment lifecycle (authorise → settle → refund) without needing separate tools for each.
Setup
The server runs in Docker and requires credentials from the Worldpay Dashboard:
git clone https://github.com/Worldpay/worldpay-mcp
docker build -t worldpay/mcp .
# Server available on port 3001
Both transport modes are supported:
- SSE (default, for remote/cloud agents):
node ./dist/server-sse.js - stdio (for local agent hosts like Claude Desktop or Cursor):
node ./dist/server-stdio.js
Relationship to Stripe Agent Toolkit
Stripe Agent Toolkit is the closest analogue and has a head start: it's framework-integrated (LangChain, CrewAI, Vercel AI SDK, OpenAI Agents SDK), has a hosted MCP server at mcp.stripe.com, and is in active use. Worldpay MCP is simpler — four tools, Docker-only, no hosted option — but it validates that payment MCP servers are a multi-vendor pattern, not a Stripe experiment.
Worldpay also supports the Agentic Commerce Protocol (ACP), giving merchants a path to reach ChatGPT shoppers through a separate, standardised commerce layer.
Why Assess, Not Trial
- Narrower tool surface — four tools vs. Stripe's dozen+; no issuing, treasury, or subscription tooling
- No hosted server — requires self-hosting; Stripe's
mcp.stripe.comlowers the bar for experimentation - No framework SDK — Worldpay MCP is a standalone server; Stripe ships first-class framework integrations
- Limited documentation — fewer integration examples compared to Stripe's mature agent docs
That said, Worldpay processes 52+ billion transactions annually across 135+ currencies and 60+ acquiring licenses. For teams already on Worldpay (especially post-GlobalPayments acquisition), this is worth evaluating — the fundamental approach is sound.
Key Characteristics
| Property | Value |
|---|---|
| Type | MCP server (self-hosted) |
| Transport | SSE (port 3001), stdio |
| Runtime | Node.js / Docker |
| GitHub | Worldpay/worldpay-mcp |
| Developer Hub | developer.worldpay.com |
| License | Open (no licensing fees) |
| Announced | November 24, 2025 |
| Parent company | GlobalPayments (acquired January 2026) |
| Related | Stripe Agent Toolkit, Agentic Commerce Protocol |