Connect Claude or ChatGPT to your MONEI account

The MONEI MCP server lets an AI assistant work with your MONEI account. Ask the assistant about your payments, customers, subscriptions or payouts, and it reads the answer from your account. With write access, it can also act for you, for example create a payment or issue a refund.

The assistant never gets your password. You sign in on the MONEI dashboard, pick one account and the permissions the assistant gets, and you can disconnect it at any time.

info

The MCP server works with Claude (the web app and Claude Desktop), Claude Code and ChatGPT (Pro, Business, Enterprise and Edu plans). Other AI assistants are not supported yet. The MCP server works with live data only: test mode and test accounts are not available.

How it works

The assistant talks to the MCP server at https://mcp.monei.com. The sign-in starts at oauth.monei.com and continues on dashboard.monei.com, where you sign in as usual (password, Google or Apple, and your second factor). If you are already signed in, the assistant goes straight to the consent page.

Add the MONEI MCP server

Claude and Claude Desktop

On a Free, Pro or Max plan:

1. In Claude, open Customize → Connectors, click + Add, then Add custom connector.

2. Enter the name MONEI and the URL, then click Continue:

   https://mcp.monei.com

3. Check the authentication settings and click Continue.

4. Under Authentication, choose Sign in now. Under OAuth client, keep Use Claude's published identity. MONEI accepts no other OAuth client.

5. Click Add. Claude opens the MONEI sign-in in your browser.

On a Team or Enterprise plan, only an Owner or a Primary Owner can add a custom connector. On Enterprise, a custom role with Manage access to Libraries can also add it:

1. The owner opens Organization settings → Connectors, clicks Add, points to Custom and selects Web.
2. The owner enters the name MONEI and the URL https://mcp.monei.com, clicks Continue, and sets Authentication and OAuth client as in steps 3 and 4 above, then clicks Add.
3. Each member opens Customize → Connectors, finds the MONEI connector and clicks Connect. Each member signs in to MONEI with their own user.

A connector you add on claude.ai is also available in Claude Desktop.

Claude Code

Run:

claude mcp add --transport http monei --scope user https://mcp.monei.com

--scope user makes the server available in every project. Without it, Claude Code adds the server to the current project only.

Then, in Claude Code, run /mcp, select monei and choose Authenticate. Claude Code opens the MONEI sign-in in your browser.

ChatGPT

Use ChatGPT on the web. What you can do depends on your ChatGPT plan:

• Business, Enterprise and Edu: Read and Write. On Business, only a workspace admin or owner can add a custom MCP server. On Enterprise and Edu, an admin gives this access by role.
• Pro: Read only. ChatGPT does not use graphql_mutation, so connect with Read.
• Free and Plus: not available.

OpenAI's help article gives the current requirements.

1. Open ChatGPT Plugins, select the plus button, then Add custom MCP server.

2. Enter the name MONEI. Under Connection, enter this Server URL:

   https://mcp.monei.com

3. For authentication, choose OAuth. Do not enter a client ID or a client secret: ChatGPT identifies itself to MONEI.

4. Review the risk warning, select I understand and want to continue, then Create as a plugin.

5. Install the plugin. When ChatGPT asks you to connect, it opens the MONEI sign-in.

On a workspace, only an admin or owner can publish the plugin to the workspace, also when a member with developer access added it. Then each member installs it and signs in to MONEI with their own user.

In a chat, type @ and select MONEI to use it.

Give access on the consent page

After you sign in, the dashboard shows the name of the assistant, for example "ChatGPT would like access to your MONEI account".

1. Account. Pick the account the assistant gets. The list shows the account selected in your dashboard and every other live account where you are an authorized user. One connection reaches one account.
2. Set permissions. Choose one:
   • Read (default): the assistant can view data and change nothing.
   • Write: the assistant can view data and act, within what your roles allow.
   • Customise: choose None, Read or Write for each area, such as Payments, Subscriptions or Customers.
3. Click Continue and review the account and the permission list.
4. Click Authorise. The dashboard sends you back to the assistant. Cancel gives no access.

The assistant never gets more than your own roles allow. If your roles change later, the access of the connection changes with them at the next request. A connection lasts 30 days; then connect again.

warning

Authorise only when you started the connection in the assistant a moment ago. If the consent page appears when you did not start a connection, click Cancel.

Claude Code and apps on your computer

Claude Code receives the access through a local address on your computer (http://localhost). For this connection, the review step shows "Authorising will redirect you to an app on this computer" instead of the address of the assistant. Any app on your computer can present itself as Claude Code. Authorise only when you started the connection in Claude Code on this computer.

What the assistant can do

The MCP server gives the assistant these tools:

Tool	What it does
graphql_schema	Describes the operations and data the assistant can use.
graphql_query	Reads data from your account, through the GraphQL API.
graphql_mutation	Changes data, for example creates a payment or issues a refund. Only with Write.
search_docs	Searches this documentation. Every connection has it, whatever the permissions.

A Read connection does not get graphql_mutation. When an action needs a permission the connection does not hold, the assistant gets an error that names it, for example Not authorized: payments:refund. To give it, connect again with Write or with that area set to Write in Customise.

Tool results hold text from other people

Many fields hold text that other people wrote: customer names, email addresses, payment descriptions, metadata and dispute messages. The assistant reads this text as part of a tool result. A customer can write text that looks like an instruction to the assistant. Treat what the assistant proposes after it reads such data with care:

• Review every action before you allow it. The assistant asks you before it uses graphql_mutation: read what it sends.
• Use Read when you only need answers.

danger

With Write, keep the approval of graphql_mutation on. In Claude, do not choose Allow always for it. In ChatGPT, do not let it remember your approval. During Research, Claude can use connector tools without asking you: use a Read connection there, or turn graphql_mutation off in the chat's tool menu.

What a connection cannot do

Some data and actions are not available to the assistant, whatever the permissions and your roles:

• Payouts and transaction types. The assistant cannot choose the transaction type of a payment, so it cannot create payouts or pre-authorizations. It cannot create or edit points of sale.
• Payment tokens and saved cards. The assistant cannot read payment tokens or a customer's saved payment methods, create a reusable payment token, or set a customer's default payment method.
• Recurring payments. The assistant cannot start a payment sequence (recurring payments or instalments) or activate a subscription.
• Lasting destinations for your data. The assistant cannot set the callback URLs of a subscription, manage webhooks, change payment processor settings or SFTP reports, or change who receives account emails.
• Users and identity. The assistant cannot manage authorized users, read identity verification data, or list the other accounts of your user.
• Credentials, bank details and files. The assistant cannot read API keys, sees your bank account number masked, and cannot create export files, download documents or contracts, or upload documents.
• Disputes and financing documents. The assistant can read chargebacks, but cannot open a dispute response with its documents, or send evidence. It cannot read financing (MONEI Capital) documents or sign your contract.
• Connected apps. The assistant cannot list or disconnect connections.

Disconnect an assistant

Settings → Connected apps lists the connections of your user on every account, with the account of each. Click Disconnect to end a connection: the next request of the assistant fails, and you must connect again to use it.

You can also remove the MCP server in the assistant:

• Claude: open Customize → Connectors and disconnect or remove the MONEI connector.
• Claude Code: run /mcp, select monei and choose Clear authentication, or run claude mcp remove monei --scope user.
• ChatGPT: remove the MONEI plugin in ChatGPT Plugins.

warning

Removing the MCP server in the assistant does not always end the access on MONEI. To be sure, disconnect the connection in Connected apps.

Common questions

Why is my account not in the list?

The list shows live accounts only. You must be an authorized user of the account. If you are the account owner and are not in Authorized users, two more conditions apply: the account's admin email must be your email, and the account must be the one selected in your dashboard. Select the account in the dashboard, then connect again.

Does the assistant see my password?

No. You sign in on dashboard.monei.com. The assistant gets a token for this connection only, and the token works only with the MONEI MCP server.

Can I use another AI assistant?

Not yet. The MCP server accepts Claude, Claude Desktop, Claude Code and ChatGPT only. To let any MCP client search the documentation without an account, use the documentation MCP server.