Learn how to connect an AI assistant to your Chargeback.io account using the Model Context Protocol (MCP).
This article covers connecting a supported AI assistant to Chargeback.io, what the connection can access, how to ask for data, and how to change an alert's status.
This article does not cover the Chargeback.io Public API. If you want to connect your own system to Chargeback.io, see Connect to the Chargeback.io API.
This connection helps you view and understand your data, and lets your assistant change an alert's status. It is not a replacement for Chargeback.io Support, and it cannot change anything else on your account.
What you can and can't do
The connection can read your data and change an alert's status. It cannot make any other change to your account.
Your assistant can:
Read alerts and their details
List and filter business accounts
Check account enrollment status
Answer questions about your data
Change an alert's status
Your assistant cannot:
Create alerts
Make a status change that isn't allowed on the platform
Change account settings
Access another user's data
Take any other action on your behalf
You can only work with data your own Chargeback.io account has permission to see.
Supported AI assistants
Setup works with:
Claude (and Claude Code)
ChatGPT (and Codex)
Grok
Cursor
Antigravity IDE
Devin
Mistral
Most other MCP-compatible clients also work. If your client has an MCP, connectors, or plugins section that supports the streamable-HTTP transport and OAuth 2.1, it will connect using the same endpoint below.
The MCP endpoint
When you set up any client, use this URL:
https://mcp.chargeback.io/mcp
No API key is needed. Authentication happens when you sign in through your browser, and the client finds the sign-in flow automatically.
How to connect
Menu names vary between clients and can change as clients update, but the flow is the same each time.
Open your AI client's MCP, connectors, or plugins settings.
Add a new connection and paste the endpoint URL:
https://mcp.chargeback.io/mcpSign in to Chargeback.io in the browser window that opens.
Review the permissions the assistant asks for. There are three: two read-only permissions for alerts and business accounts, and one that lets the assistant change an alert's status.
Approve access. All three permissions are needed for the full feature set.
You're connected and can start asking questions.
Already connected? Reconnect
If you set up this connection before status changes were available, it was approved for read-only access. It keeps working for reading your data, but it can't change an alert's status until you approve the new permission.
To reconnect:
Open your AI client's MCP, connectors, or plugins settings.
Disconnect or remove the existing Chargeback.io connection.
Add it again using the same endpoint URL.
Sign in and approve all three permissions.
Some clients prompt you to approve the new permission on their own the next time you use the connection. If yours does, you can approve it there instead of reconnecting manually.
How to ask for data
The way you phrase a question affects what you get back. Specific questions return specific answers.
Questions that work well:
"Show me all refunded Ethoca alerts from the last 7 days"
"How many alerts did [business account] have in June?"
"List business accounts with incomplete enrollment status"
"Get alert [ID] and summarize what happened"
Questions that work poorly:
"Show me everything"
"What's going on with my chargebacks?"
"Are things looking good?"
Being specific about the time range, account, status, or ID lets the assistant form a precise query. Vague questions may return partial data or trigger a chain of clarifying questions.
Change an alert's status
Once you've approved all three permissions, you can ask your assistant to change an alert's status instead of opening the Dashboard.
For example:
"I refunded this one in Stripe. Mark alert [ID] as Manually Refunded"
"I couldn't find this transaction in my processor. Set alert [ID] to Not Found"
"Update alerts [ID], [ID], and [ID] to Manually Refunded"
Always include the alert ID. Asking the assistant to update "the last one" or "that alert" is how the wrong alert gets changed.
The same rules apply. Every restriction on status transitions works exactly as it does in the Dashboard. If a status change isn't allowed on the platform, your assistant can't make it either.
Your assistant reports back what it did, but it can misread which alert you meant, especially when you're working through several at once. Confirm the change in your Dashboard before you move on.
Limitations
AI interpretation can be wrong. The assistant fetches real data but may summarize, compare, or total it incorrectly. Verify anything decision-critical in your Dashboard.
Status changes are the only change it can make. The assistant cannot create alerts, change account settings, or modify anything else, and it cannot make a status transition the platform blocks.
Data reflects the moment you ask. The assistant fetches fresh data each time and has no memory of earlier queries between sessions. Ask again for an updated snapshot.
Only alerts and business accounts are available. Invoices, API keys, billing, and account configuration are not accessible through the connection. Use the Dashboard or the Public API for those.
Some AI plans limit MCP functionality. Lower-tier plans on some AI platforms may restrict tool calls or how much data can be retrieved in one session. If the assistant stops mid-query or says it can't access external tools, your plan's limits may be the reason.
Security and permissions
During setup, you approve the permissions the assistant can use. There are three: two read-only and one that lets the assistant change an alert's status. All three are needed for the full feature set.
Connections use short-lived access tokens that last 24 hours and longer-lived refresh tokens that last 90 days. Revoking a connection invalidates both immediately.
The MCP server holds no copy of your data. Every request is forwarded in real time to Chargeback.io's API under your credentials. Only data your account can see is ever returned, and any status change is made under the same permissions your account already has.
Security tips
Turn on confirmation for tool calls. If your AI client offers a "confirm before executing" or human-in-the-loop setting, enable it. Your assistant can change alert statuses now, so this lets you approve each change before it runs.
Never paste credentials or sensitive data into the chat. You never need to share passwords, API keys, or card numbers. The connection fetches your data securely in the background.
Be careful with untrusted content. Text inside external data, such as an alert's contents or an account name, can be written to influence how an assistant behaves. If you have several MCP servers connected at once, be cautious about unverified data flowing between them. If the assistant reports something unexpected, check the raw data in your Dashboard instead of acting on its interpretation.
Don't share sessions that have Chargeback.io connected. Anyone you share a conversation with can see the data the assistant retrieved.
Revoke connections you no longer use. Refresh tokens stay valid for 90 days, so an idle connection is still live access until you remove it.
Verify sensitive figures in the Dashboard before you act on any count, total, or date the assistant gives you.
When the assistant can't help
If a request can't be fulfilled, the assistant tells you why and suggests a next step. Common cases:
No results: The filter matched nothing, or the ID doesn't exist.
No access: You asked for data on an account that isn't linked to your profile.
Permission not approved: You asked for a status change, but the connection was set up before status changes were available. See Already connected? Reconnect.
Out of scope: You asked for a status change the platform doesn't allow, or for data outside alerts and business accounts. Make other changes in the Dashboard, or contact Support.
đŹ Still need help? Contact Chargeback.io Support.