Askacharge.com — EV charging network

What askacharge.com — EV charging network does

askacharge.com — EV charging network gives MCP-compatible agents access to the askacharge.com Charging Station Management System. The platform manages EV charge points connected through OCPP 1.6J and 2.0.1. Through the MCP interface, an agent can inspect charger connectivity, connector details, active charging activity, historical sessions, faults, tariffs, electricity prices, customers, power limits, and operational KPIs.

The server also exposes actions that affect physical equipment. These include starting or stopping a charge, rebooting a charger, changing its availability, unlocking a connector, requesting a current status message, and requesting diagnostics. Other write operations register chargers, create tariffs and fleet customers, authorize RFID tags, or add simulated chargers for testing. An API escape hatch can invoke other permitted operations from the platform's REST API.

How it works

The service is hosted at https://askacharge.com/askacharge/api/mcp; there is no local package to install. Requests use JSON-RPC 2.0 over HTTP POST with the streamable-HTTP transport. The endpoint accepts MCP protocol versions 2025-06-18, 2025-03-26, and 2024-11-05. It does not provide an SSE stream, and GET requests return 405.

The endpoint can respond to initialization, ping, and tool-list requests without credentials. Tool calls require a brand API key supplied as either Authorization: Bearer ... or X-Api-Key. Each key belongs to one brand, so its data access is limited to that brand. Scopes determine which tools appear and which operations are permitted. Command permissions can be granted individually, and location restrictions can limit where commands may act.

Hardware commands return an immediate charger acknowledgement and a job_id, but the physical result may arrive later through OCPP. Agents should query the command-status tool with that job ID rather than repeat the original operation. Statuses include acknowledged, confirmed, timed out, rejected, and failed states.

Setup and configuration

Create an askacharge.com account, obtain an API key from the panel's API keys area, and configure the remote MCP URL in a client that supports HTTP MCP connections. Claude Code can register the endpoint with its HTTP transport and an authorization header. Clients using JSON configuration can define the server URL and header directly.

No environment variable is required by the hosted endpoint itself.

Tools and capabilities

The catalogue contains 25 tools, with Spanish tool names and descriptions. Capabilities include:

• Listing chargers and viewing detailed charger records.
• Checking live connectivity, active sessions, drawn power, incidents, and command progress.
• Reviewing sessions, revenue, energy, costs, customers, tariffs, PVPC prices, and location power limits.
• Sending OCPP remote-start, remote-stop, reset, availability, unlock, status-trigger, and diagnostics requests.
• Creating chargers, tariffs, fleet customers, RFID tags, and up to 10 simulated OCPP chargers.
• Calling other askacharge.com API operations through the authenticated API tool.

Limitations and notes

The tool names and descriptions are in Spanish. A location-scoped key restricts command targets but does not restrict read listings, which can still return the brand's wider data. There is no separate sandbox; trial-mode brands are the documented way to test without affecting a production setup.

The MCP layer uses the platform's existing REST API permissions, audit trail, rate limits, and idempotency behavior. Remote commands can affect physical hardware, stop live sessions, or reboot chargers, so agents should confirm intent and track the returned job ID. The service is request/response based and does not offer an SSE stream.