Connect Chargekeeper to Claude (MCP)
Chargekeeper provides an MCP (Model Context Protocol) server. Once connected to Claude, it lets you query your fleet in natural language: charging station status, errors, ongoing sessions, invoices, pricing, alerts… and, depending on the rights granted, act on your charging stations.
1. Get your MCP connection secret
To get started, the Chargekeeper connection team must provide you with an MCP connection secret. Contact the sales team or the connection team to request one.
You will receive two pieces of information:
| Information | Description |
|---|---|
| Tenant | The identifier of your Chargekeeper space (for example mon-cpo). |
| MCP API key | The secret that allows Claude to access your space. |
The MCP API key is a secret: store it in a password vault and do not share it.
Rights attached to the key
Rights are set on the key by the Chargekeeper team. Specify what you need in your request:
| Right | What it allows |
|---|---|
| Read diagnostics | View charging station status, sessions and errors |
| Read configuration | View the OCPP configuration of charging stations |
| Modify configuration | Modify the OCPP configuration of charging stations |
| Non-critical actions | Clear a charging station's cache, request an OCPP message from it, set a connector back to operative |
| Critical actions | Reset a charging station, unlock a connector, set a connector to inoperative |
A key can also:
- run in confirmation mode: Claude must then obtain explicit confirmation before each sensitive action (reset, unlock, set inoperative, configuration change);
- be restricted to specific charging stations only;
- have an expiry date.
For viewing only, ask for a read-only key. Modification and action rights act on real charging stations.
2. Open Claude settings
- Sign in to your Claude account at https://claude.ai/.
- Click your name at the bottom left, then Settings.

3. Add the Chargekeeper connector
- In the settings menu, click Connectors.
- Click the Add button.

- In the custom connector window:
- first field (name): enter
Chargekeeper; - MCP server URL: enter
https://mcp.service-evse.com/mcp.
- first field (name): enter
- Click Continue.

4. Sign in with your secret
A Chargekeeper sign-in page opens:
- Tenant: enter the identifier of your space (e.g.
mon-cpo). - MCP API key: paste your key.
- Click the sign-in button.

An authorization page then shows your space, the permissions and the list of available tools. Approve access: you are redirected to Claude.
The rights actually applied are those of the MCP API key. To extend or restrict what Claude can do, the key itself must be changed.
5. Choose when Claude can use the tools
The Chargekeeper connector now appears in Settings → Connectors. Click it: the tool permissions section lets you choose, for all tools or tool by tool:
- ✓ (check mark): Claude uses the tool without asking you;
- ✋ (hand) — requires approval: Claude asks for your consent before each use;
- ⃠ (crossed-out circle): Claude cannot use the tool.

Keep approval required at least for the tools that act on charging stations: Change Availability, Change Charger Configuration, Clear Cache, Reset Charger, Trigger Message, Unlock Connector.
The Disconnect button removes Claude's access to your Chargekeeper space.
6. Use the connector
In a new conversation, enable the Chargekeeper connector from the tools menu below the input box, then ask your question. Examples:
- “Which charging stations are currently in error?”
- “Show me the reboot history of charging station ACME-001.”
- “Were there any abnormal sessions this week?”
- “Which pricing applies to the North Car Park site area?”
The connection is kept: Claude renews access automatically, without asking for the key in each conversation. After 30 days without use, you will need to sign in again.
Limits
- The number of MCP tool calls is limited per month and per space (5,000 by default). Ask Claude “What is my MCP quota?” to see your usage.
- If the key is disabled, expired or deleted, Claude loses access: request a new key and reconnect the connector.
Troubleshooting
| Situation | Solution |
|---|---|
| Sign-in is refused | Check the tenant (identifier only, without https:// or domain name) and the key. If the error persists, the key may be expired or disabled: contact the connection team. |
| An action is refused | The key does not have the required right, or the charging station is not among the stations allowed for the key. |