Connect AI agents to FloPayCopy Anchor Link

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.

Staging and production have separate MCP servers, accounts, and data. Add one connector for each environment to use them side by side, and sign in with that environment's FloPay account.

Both environments use the same protocol and access flow:

What agents can doCopy Anchor Link

• 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 payments, manage gateway credentials, control subscriptions, configure webhooks, update catalog records, and run other reviewed high- and critical-risk actions. 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 reviewed exclusions and explains the surfaces that stay outside the merchant MCP boundary.

ConnectCopy Anchor Link

1. Check Client support for Claude.ai, ChatGPT, and Grok, then follow the guide for your client.
2. 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.

Name the connectors FloPay Stage and FloPay Production so you can distinguish them. Both can be enabled in the same chat; explicitly name the target environment in each request, for example, "Use FloPay Stage to show my company details." See the Claude.ai, ChatGPT, or Grok guide.

Operate safelyCopy Anchor Link

• 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.