mcp-openchargemap
Open Charge Map MCP — global EV charging station database (openchargemap.io).
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Power your agent
पब्लिशर का अपना URL। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
https://gateway.pipeworx.io/openchargemap/mcpऊपर दिया Claude बटन नाम और URL भरकर Claude खोलता है। पुष्टि आपको वहीं करनी होती है।
claude mcp add --transport http io.github.pipeworx-io-openchargemap https://gateway.pipeworx.io/openchargemap/mcpRun in a terminal.
{ "mcpServers": { "io.github.pipeworx-io-openchargemap": { "command": "npx", "args": [ "-y", "mcp-remote", "https://gateway.pipeworx.io/openchargemap/mcp" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
Open Charge Map MCP — global EV charging station database (openchargemap.io).
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Open Charge Map MCP — global EV charging station database (openchargemap.io).
| Tool | Description |
|---|---|
find_stations | Find EV charging stations (electric vehicle chargers) near a place. Pass a location name (city/place, e.g. "San Francisco", "Berlin", "Austin TX") and it is geocoded automatically — OR pass explicit latitude+longitude. Returns nearby charging stations with operator, status, available connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), and distance. Filter by connector type to find e.g. only CCS or Tesla chargers. |
get_station | Get full detail for a single EV charging station by its Open Charge Map POI ID. Returns the connector types (CCS/CHAdeMO/Tesla connectors), charging speed (kW), operator, status, plus user comments and last-verified date. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"openchargemap": {
"url": "https://gateway.pipeworx.io/openchargemap/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/openchargemap/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/openchargemap_find_stations \
-H 'Content-Type: application/json' \
-d '{"location":"San Francisco","max_results":10}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/openchargemap_find_stations. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"openchargemap": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-openchargemap"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-openchargemap
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Openchargemap data" })
The gateway picks the right tool and fills the arguments automatically.
MIT
Open Charge Map MCP — global EV charging station database (openchargemap.io).
{ "mcpServers": { "io.github.pipeworx-io-openchargemap": { "url": "https://gateway.pipeworx.io/openchargemap/mcp", "headers": {} } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए http कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
पब्लिशर ने ये एनवायरनमेंट वेरिएबल बताए हैं: PIPEWORX_API_KEY।
Openchargemap तक HTTP से पहुँचा जाता है।
पिछली जाँच 2026-11-10 को हुई। Open Charge Map MCP — global EV charging station database (openchargemap.io).