Connect Claude.ai
Add FloPay MCP to Claude.ai as a custom connector, sign in with your FloPay account, and check a cited knowledge read and a read-only tool call.
Connect Claude.ai
Claude.ai connects to remote MCP servers as custom connectors. This guide adds FloPay MCP as one and checks that it works. Before you rely on it, see Client support for the latest recorded compatibility runs for Claude.ai.
The Claude.ai menu names below follow Anthropic's custom connector guide. If Claude.ai has changed since, follow that guide and use the FloPay details from this page.
Before you start
- A FloPay merchant operator account. Confirmed actions need the
owneroradminrole on the merchant. - A Claude plan that includes custom connectors. On Team and Enterprise plans, an organization owner adds the connector first.
- The FloPay MCP server URL:
https://mcp.flopay.com/mcp.
Add FloPay MCP
On a Pro or Max plan:
- Go to Customize > Connectors.
- Select +, then Add custom connector.
- Enter
https://mcp.flopay.com/mcpas the remote MCP server URL. - Leave Advanced settings empty. FloPay supports dynamic client registration, so no OAuth client ID or secret is needed.
- Select Add.
On a Team or Enterprise plan, an owner goes to Organization settings > Connectors, selects Add, chooses Custom > Web, and enters the same URL. Each member then opens Customize > Connectors, finds FloPay MCP, and selects Connect.
Sign in and approve
When you connect, Claude.ai opens FloPay's sign-in page:
- Sign in with your FloPay account.
- Review the access Claude.ai is asking for. It should include
mcp:read, andmcp:writeif you want confirmed actions. - Choose the merchant Claude.ai works for, and approve.
To work with a different merchant later, disconnect and connect again, choosing the other merchant.
Check the connection
- Start a new chat, select + at the bottom left, open Connectors, and turn on FloPay MCP.
- Ask: "Search the FloPay developer documentation for how FloPay MCP sign-in works, and give me the source link." Claude.ai should answer from a FloPay knowledge resource and include a source link to a FloPay page.
- Ask: "Use FloPay to show my company details." Claude.ai should call
Company_get. Check that the merchant slug and currency match the merchant you approved.
If Claude.ai finds no FloPay tools, the sign-in did not grant mcp:read. Disconnect, connect again, and check the requested access. Limits and errors explains any other error Claude.ai reports.
Confirmed actions
FloPay only offers mutating tools to a client that declares it can show confirmation forms, and Client support records whether Claude.ai passed the confirmed action checks. When Claude.ai does show a FloPay confirmation:
- Read the preview in the form before you accept: it lists each change with its values before and after.
- If the form asks for an idempotency key, enter a new unique value, and reuse that value only to retry the same action.
- Decline anything you did not ask for. A declined action never reaches your FloPay account.
Confirmed actions explains previews, expiry, and retries in full.
Disconnect
Go to Customize > Connectors, select FloPay MCP, and choose Remove. Claude.ai stops using FloPay straight away, and any FloPay access token it already holds expires within about 15 minutes.
For a client other than Claude.ai, ChatGPT, or Grok, follow Connect any MCP client.
Client support
Which hosted AI clients FloPay has certified for FloPay MCP, tested separately for read-only tools and knowledge and for confirmed actions.
Connect ChatGPT
Connect FloPay MCP to ChatGPT in developer mode, sign in with your FloPay account, and check a cited knowledge read and an authorized read-only tool call.