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, and how to ask for data.
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. It is not a replacement for Chargeback.io Support, and it cannot take any action on your account.
What you can and can't do
The connection is read-only.
Your assistant can:
Read alerts and their details
List and filter business accounts
Check account enrollment status
Answer questions about your data
Your assistant cannot:
Create or modify alerts
Change account settings
Access another user's data
Take any action on your behalf
You can only retrieve 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.
Select the data the assistant can access. We recommend selecting both alerts and business accounts, because the connection is read-only.
Approve access.
You're connected and can start asking questions.
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.
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.
The connection is read-only. The assistant cannot resolve alerts, change settings, or modify anything. If it says it made a change, it's mistaken. Check the Dashboard.
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 choose which data the assistant can access. Because the connection is read-only, there is no risk in enabling both alerts and business accounts.
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, and only data your account can see is ever returned.
Security tips
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.
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.
Out of scope: You asked the assistant to change something, or for data outside alerts and business accounts. Make those changes in the Dashboard, or contact Support.
💬 Still need help? Contact Chargeback.io Support.