MCP servers
Monta provides two MCP (Model Context Protocol) servers. They serve different purposes — make sure you connect to the right one:
| Monta API MCP | Docs Search MCP | |
|---|---|---|
| URL | https://partner-api-mcp.monta.app/mcp | https://docs.partner-api.monta.com/mcp |
| Purpose | Query and manage your account's live data — teams, charge points, charging sessions, pricing, webhooks | Search and explore the API documentation — endpoints, parameters, schemas |
| Authentication | Required (Monta API credentials) | None (anonymous) |
| Tools | One tool per API endpoint (180+, filtered by your credential scopes) | 4 spec-search tools (list-endpoints, get-endpoint, search-endpoints, execute-request) |
| Best for | AI assistants operating your charging infrastructure | AI coding assistants writing integration code against the API |
Monta API MCP (account-connected)
The Monta API MCP server at https://partner-api-mcp.monta.app exposes every Monta API endpoint as an MCP tool, authenticated with your own credentials. Connected assistants can list your teams, inspect charge point status, start and stop charging sessions, configure pricing, and more — using your real account data.
Get credentials
Create a Monta API key (Client ID and Client Secret) in Monta Hub — see Access and set up API keys in Monta Hub. The tools available to you depend on the scopes you grant the key: full all scope exposes every endpoint, while all:read + all:write hides delete operations.
Endpoints
| Transport | URL |
|---|---|
| Streamable HTTP (recommended) | https://partner-api-mcp.monta.app/mcp |
| SSE (legacy clients) | https://partner-api-mcp.monta.app/sse |
Authentication
Pass credentials as HTTP headers using any of these formats:
| Method | Header(s) |
|---|---|
| Combined (simplest) | X-Monta-Auth: clientId:clientSecret |
| Separate headers | X-Monta-Client-Id: clientId + X-Monta-Client-Secret: clientSecret |
| Basic auth | Authorization: Basic base64(clientId:clientSecret) |
| Bearer token | Authorization: Bearer accessToken |
Client setup
Add the server with a single command:
claude mcp add --transport http monta-partner-api https://partner-api-mcp.monta.app/mcp \
--header "X-Monta-Auth: YOUR_CLIENT_ID:YOUR_CLIENT_SECRET"Verify with claude mcp list, then ask Claude Code e.g. "List my Monta teams".
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"monta-partner-api": {
"url": "https://partner-api-mcp.monta.app/mcp",
"headers": {
"X-Monta-Auth": "YOUR_CLIENT_ID:YOUR_CLIENT_SECRET"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"monta-partner-api": {
"serverUrl": "https://partner-api-mcp.monta.app/mcp",
"headers": {
"X-Monta-Auth": "YOUR_CLIENT_ID:YOUR_CLIENT_SECRET"
}
}
}
}Claude Desktop runs the MCP adapter locally via a small launcher script. Follow the Claude Desktop setup guide.
Replace YOUR_CLIENT_ID and YOUR_CLIENT_SECRET with your actual credentials.
Other integrations
- n8n — MCP Client Tool node
- ChatGPT — custom GPT Actions
- CLI — every endpoint as a terminal command (
npm install -g @monta-api/cli) - Full tool reference — always-up-to-date list of every MCP tool
Try it
Once connected, ask your assistant things like:
Show me all my charge points and their current state
Start a charging session at charge point 12345
Show me charging sessions from the last 24 hours
Docs Search MCP (documentation only)
This documentation site also hosts its own MCP server at https://docs.partner-api.monta.com/mcp. It is not connected to your Monta account — it exposes 4 anonymous tools for searching this documentation: list-endpoints, get-endpoint, search-endpoints, and execute-request.
Use it in AI code editors (Cursor, Windsurf, etc.) while writing integration code, so the assistant can look up endpoint definitions and schemas without leaving the editor:
{
"mcpServers": {
"monta-partner-api-docs": {
"url": "https://docs.partner-api.monta.com/mcp"
}
}
}To work with your account's live data, use the Monta API MCP above instead.
Updated 14 days ago