FloPay MCP
Connect AI agents to FloPay with MCP. Sign in with OAuth, search developer knowledge, call reviewed merchant tools, and confirm every change.
Connect AI agents to FloPay
FloPay MCP connects AI agents to FloPay through the Model Context Protocol. An agent signs in with OAuth on behalf of a merchant operator, searches FloPay developer knowledge, reads merchant data, and runs a reviewed set of actions after the operator confirms each one. It works with any client that follows the protocol, whichever model runs behind it.
| Detail | Value |
|---|---|
| MCP endpoint | https://mcp.flopay.com/mcp |
| Protected resource metadata | https://mcp.flopay.com/.well-known/oauth-protected-resource |
| Authorization server | https://api.flopay.com |
| Protocol version | 2026-07-28 |
| Transport | HTTP POST with JSON responses, and no session |
| Scopes | mcp:read for knowledge and read-only tools, mcp:write for confirmed actions |
What agents can do
- Search FloPay knowledge. Find documentation, REST reference, SDK guidance, and changelog entries without knowing a resource URI, each with a link to its canonical source. See Knowledge resources.
- Read merchant data. Call read-only tools for payments, subscriptions, disputes, products, checkouts, customers, and settings. See Verify results to check what a tool returned.
- Run confirmed actions. Create checkout links, update catalog records and branding, record dispute review decisions, and make other low- and medium-risk changes. Every action returns a preview first and runs only after explicit confirmation. See Confirmed actions.
Every tool comes from FloPay's reviewed API contract. The Tool reference documents each tool's arguments, results, errors, and access policy. Unavailable operations lists what agents cannot do, including high-risk actions such as creating payments or changing gateway credentials.
Connect
- Check Client support for Claude.ai, ChatGPT, and Grok, then follow the guide for your client.
- For any other MCP client, follow Connect any MCP client. It covers discovery, OAuth with PKCE, a first knowledge read, and a first tool call.
The operator signs in with their FloPay account and chooses the merchant the agent works for. The agent can only do what the operator's role and the granted scopes allow, and FloPay checks both again on every call.
Operate safely
- Limits and errors: concurrency, size, time, and rate limits, and how to recover from each error.
- Verify results: contract revisions, status codes, correlation IDs, aggregate context, and knowledge sources for checking a result before you rely on it.
- Data handling and security: how FloPay MCP treats credentials and what it records, handling personal data in results, and guarding against prompt injection.
Worldpay Corporate Gateway
Preview guidance for connecting a Worldpay Corporate Gateway merchant code to FloPay, covering credentials, connection tests, approval, and current limits.
Connect any MCP client
Connect a standards-based MCP client to FloPay. Discover the authorization server, sign in with OAuth and PKCE, then read knowledge and call a tool.