io.github.cyanheads/openchargemap-mcp-server
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
What can you do with io.github.cyanheads/openchargemap-mcp-server?
- Type-safe client for the OCM v3 POI API with retry and session-scoped result caching
- Reference data (connectors, operators, usage/status types, countries) bundled as an offline snapshot — name→ID resolution needs no live
/referencedatacall, with an optional startup refresh to prevent drift - Curated connector aliases (
CCS,NACS/Supercharger,J1772,Type 2,CHAdeMO) so the names agents actually use resolve to the right IDs - Geocoding intentionally delegated — the server is coordinate-native and composes with any geocoding MCP server (e.g. the
openstreetmapserver'sopenstreetmap_search_places) rather than rebuilding place-name lookup - Stations are addressed by numeric OCM ID, discovered through
openchargemap_find_stations— the OCM API has no UUID lookup - Reliability surfaced as first-class signal —
status,statusTypeId,isOperational, anddateLastVerifiedon every station, plus a plain-prosereliabilityNotederived only from observable facts (no fabricated confidence score) - Honest sparsity — heavily-omitted upstream fields are optional with "absence means unknown, not zero/false" descriptions; the server never invents data OCM didn't return
- CC BY 4.0 attribution on every tool response and in the server-level instructions, per the data license
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http openchargemap-mcp-server 'https://openchargemap.caseyjhand.com/mcp'
{
"mcpServers": {
"openchargemap-mcp-server": {
"type": "http",
"url": "https://openchargemap.caseyjhand.com/mcp"
}
}
}
@cyanheads/openchargemap-mcp-serverclaude mcp add openchargemap-mcp-server -e 'OPENCHARGEMAP_CLAMP_LIMITS=true' -e 'OPENCHARGEMAP_API_KEY=<your openchargemap_api_key>' -e 'OPENCHARGEMAP_BASE_URL=<OPENCHARGEMAP_BASE_URL>' -e 'OPENCHARGEMAP_REFERENCE_REFRESH=false' -e 'MCP_LOG_LEVEL=info' -- npx -y @cyanheads/openchargemap-mcp-server@0.2.0
{
"mcpServers": {
"openchargemap-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/openchargemap-mcp-server@0.2.0"
],
"env": {
"OPENCHARGEMAP_CLAMP_LIMITS": "true",
"OPENCHARGEMAP_API_KEY": "<your openchargemap_api_key>",
"OPENCHARGEMAP_BASE_URL": "<OPENCHARGEMAP_BASE_URL>",
"OPENCHARGEMAP_REFERENCE_REFRESH": "false",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Environment variables
OPENCHARGEMAP_CLAMP_LIMITSClamp oversized positive integer page sizes to the tool maximum; false restores rejection.OPENCHARGEMAP_API_KEYrequired secret Open Charge Map API key, sent as the X-API-Key header on every request. Free instant signup at openchargemap.org.OPENCHARGEMAP_BASE_URLOverride the OCM API base URL (default https://api.openchargemap.io/v3). For a private mirror or testing.OPENCHARGEMAP_REFERENCE_REFRESHWhen true, refresh reference data from the live /referencedata endpoint at startup, falling back to the bundled snapshot on failure.MCP_LOG_LEVELSets the minimum log level for output (e.g., 'debug', 'info', 'warn').
@cyanheads/openchargemap-mcp-serverclaude mcp add openchargemap-mcp-server -e 'OPENCHARGEMAP_CLAMP_LIMITS=true' -e 'MCP_TRANSPORT_TYPE=<MCP_TRANSPORT_TYPE>' -e 'OPENCHARGEMAP_API_KEY=<your openchargemap_api_key>' -e 'OPENCHARGEMAP_BASE_URL=<OPENCHARGEMAP_BASE_URL>' -e 'OPENCHARGEMAP_REFERENCE_REFRESH=false' -e 'MCP_HTTP_HOST=127.0.0.1' -e 'MCP_HTTP_PORT=3010' -e 'MCP_HTTP_ENDPOINT_PATH=/mcp' -e 'MCP_AUTH_MODE=none' -e 'MCP_LOG_LEVEL=info' -- npx -y @cyanheads/openchargemap-mcp-server@0.2.0
{
"mcpServers": {
"openchargemap-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/openchargemap-mcp-server@0.2.0"
],
"env": {
"OPENCHARGEMAP_CLAMP_LIMITS": "true",
"MCP_TRANSPORT_TYPE": "<MCP_TRANSPORT_TYPE>",
"OPENCHARGEMAP_API_KEY": "<your openchargemap_api_key>",
"OPENCHARGEMAP_BASE_URL": "<OPENCHARGEMAP_BASE_URL>",
"OPENCHARGEMAP_REFERENCE_REFRESH": "false",
"MCP_HTTP_HOST": "127.0.0.1",
"MCP_HTTP_PORT": "3010",
"MCP_HTTP_ENDPOINT_PATH": "/mcp",
"MCP_AUTH_MODE": "none",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Environment variables
OPENCHARGEMAP_CLAMP_LIMITSClamp oversized positive integer page sizes to the tool maximum; false restores rejection.MCP_TRANSPORT_TYPESelects the HTTP transport.OPENCHARGEMAP_API_KEYrequired secret Open Charge Map API key, sent as the X-API-Key header on every request. Free instant signup at openchargemap.org.OPENCHARGEMAP_BASE_URLOverride the OCM API base URL (default https://api.openchargemap.io/v3). For a private mirror or testing.OPENCHARGEMAP_REFERENCE_REFRESHWhen true, refresh reference data from the live /referencedata endpoint at startup, falling back to the bundled snapshot on failure.MCP_HTTP_HOSTThe hostname for the HTTP server.MCP_HTTP_PORTThe port to run the HTTP server on.MCP_HTTP_ENDPOINT_PATHThe endpoint path for the MCP server.MCP_AUTH_MODEAuthentication mode to use: 'none', 'jwt', or 'oauth'.MCP_LOG_LEVELSets the minimum log level for output (e.g., 'debug', 'info', 'warn').
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
@cyanheads/openchargemap-mcp-server
Find EV charging stations worldwide by location and connector from the global Open Charge Map registry — full station detail, reference-ID resolution, and community reliability check-ins via MCP. STDIO or Streamable HTTP.
4 Tools • 1 Resource
Public Hosted Server: https://openchargemap.caseyjhand.com/mcp
Overview
EV charging stations from the global Open Charge Map registry. Search by location and connector, pull full station detail, resolve connector and network names to filter IDs, and read community reliability check-ins from any MCP client. Runs as a stdio process, a local Streamable HTTP server, or the public hosted endpoint above.
Tools
| Tool | Description |
|---|---|
openchargemap_find_stations | Find charging stations near a point or within a bounding box, filtered by connector, power, network, usage, status, and charge points. Coordinate-native. |
openchargemap_get_station | Full record for one station by numeric OCM ID — every connection, operator, access rules, charge points, cost, media, and a computed reliability note. |
openchargemap_lookup_reference | Resolve connector/operator/usage/status/country names to the integer filter IDs find_stations needs. Served from a bundled snapshot — offline and instant. |
openchargemap_get_station_comments | Community check-ins for one station alongside the registry status and last-verified date, so registry-vs-reality mismatch is visible. |
Resources
| Resource | Description |
|---|---|
openchargemap://station/{id} | Full station record (with community comments) by numeric OCM ID — the URI-addressable twin of openchargemap_get_station. |
All station data is also reachable via the tools; the station corpus (~200k locations, geo-scoped) isn't exposed as a listable resource, and reference data is served by openchargemap_lookup_reference rather than a resource.
Capability reference
openchargemap_find_stations tool
- Radius search (
latitude+longitude+distance,distanceUnitKMorMiles, max 500) orboundingbox— exactly one mode per call; optionalcountrycode(ISO 3166-1 alpha-2) and filtersconnectiontypeid,minpowerkw,operatorid,usagetypeid,levelid,statustypeid,minchargepoints(the ID filters take one integer ID or an OR-matched array, resolved viaopenchargemap_lookup_reference) maxresultscaps the page (default 25, max 200) andoffsetpages through up to 500 stations per search;totalCountis exact only when OCM's candidate page came back short of its cap — otherwise it's a floor, and thenoticesays which- Fails with
invalid_location(no search area, half a center, or a coordinate beside aboundingbox),no_stations,auth_failed, orupstream_unavailable
openchargemap_get_station tool
- Full record for one station by numeric OCM
id— every connection, operator/network, usage and access rules, charge-point count, usage cost, data provider, media, anddateLastVerified;includeCommentsadds every check-in inline, unpaged (useopenchargemap_get_station_commentsfor a heavily-commented station) reliabilityNoteis plain prose computed from observable facts (verification age, registry status, operational flag, fault-vs-positive check-ins), omitted when there is nothing to flag; fails withnot_found,auth_failed, orupstream_unavailable
openchargemap_lookup_reference tool
category(connectiontypes,operators,usagetypes,statustypes,currenttypes,levels,countries) plus an optional case-insensitivequerynaming a title, code, or alias ("CCS","Tesla Supercharger","FR"); omitqueryto browse the category (limitmax 100, default 25, paged viaoffset/nextOffset)- Returns the matching
id(s), thefilterParamthey feed intoopenchargemap_find_stations, andsource(liveorbundled) with asnapshotDate— answered offline from the bundled snapshot unlessOPENCHARGEMAP_REFERENCE_REFRESHrefreshed it at startup; fails withno_match
openchargemap_get_station_comments tool
- Check-ins for one station by numeric OCM
id, newest first, each with rating, date, and recorded outcome —maxresultscaps the page (default 25, max 100), paged viaoffset/nextOffset;totalCommentscounts the station's whole set, andreliabilityNote's fault ratio is computed over all of it - Returns the registry status,
isOperational, anddateLastVerifiedbeside the comments; an emptycomments: []is not an error (no reports is not evidence the charger works); fails withnot_found,auth_failed, orupstream_unavailable
openchargemap://station/{id} resource
- Full record for one station by numeric OCM ID, community comments always included — the URI-addressable twin of
openchargemap_get_station, cached for 600 seconds, and not listable - Fails with
not_foundwhen the ID doesn't resolve to a station
Features
Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
Open Charge Map-specific:
- Type-safe client for the OCM v3 POI API with retry and session-scoped result caching
- Reference data (connectors, operators, usage/status types, countries) bundled as an offline snapshot — name→ID resolution needs no live
/referencedatacall, with an optional startup refresh to prevent drift - Curated connector aliases (
CCS,NACS/Supercharger,J1772,Type 2,CHAdeMO) so the names agents actually use resolve to the right IDs - Geocoding intentionally delegated — the server is coordinate-native and composes with any geocoding MCP server (e.g. the
openstreetmapserver'sopenstreetmap_search_places) rather than rebuilding place-name lookup - Stations are addressed by numeric OCM ID, discovered through
openchargemap_find_stations— the OCM API has no UUID lookup
Agent-friendly output:
- Reliability surfaced as first-class signal —
status,statusTypeId,isOperational, anddateLastVerifiedon every station, plus a plain-prosereliabilityNotederived only from observable facts (no fabricated confidence score) - Honest sparsity — heavily-omitted upstream fields are optional with "absence means unknown, not zero/false" descriptions; the server never invents data OCM didn't return
- CC BY 4.0 attribution on every tool response and in the server-level instructions, per the data license
Getting started
Public Hosted Instance
A public instance is available at https://openchargemap.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP, with this client config:
{
"mcpServers": {
"openchargemap-mcp-server": {
"type": "streamable-http",
"url": "https://openchargemap.caseyjhand.com/mcp"
}
}
}
Self-Hosted / Local
Add the following to your MCP client configuration file. An Open Charge Map API key is required — see Prerequisites.
{
"mcpServers": {
"openchargemap-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/openchargemap-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"OPENCHARGEMAP_API_KEY": "your-api-key"
}
}
}
}
Or with npx (no Bun required):
{
"mcpServers": {
"openchargemap-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/openchargemap-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info",
"OPENCHARGEMAP_API_KEY": "your-api-key"
}
}
}
}
Or with Docker:
{
"mcpServers": {
"openchargemap-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "MCP_TRANSPORT_TYPE=stdio",
"-e", "OPENCHARGEMAP_API_KEY=your-api-key",
"ghcr.io/cyanheads/openchargemap-mcp-server:latest"
]
}
}
}
For Streamable HTTP, set the transport and start the server:
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 OPENCHARGEMAP_API_KEY=... bun run start:http
# Server listens at http://localhost:3010/mcp
Prerequisites
- Bun v1.4 or higher (or Node.js v24+).
- An Open Charge Map API key — free instant signup: register an application at openchargemap.org. Sent as the
X-API-Keyheader on every request; the server fails fast at startup if it's unset.
Installation
- Clone the repository:
git clone https://github.com/cyanheads/openchargemap-mcp-server.git
- Navigate into the directory:
cd openchargemap-mcp-server
- Install dependencies:
bun install
- Configure environment:
cp .env.example .env
# edit .env and set OPENCHARGEMAP_API_KEY
Configuration
All configuration is validated at startup via Zod schemas in src/config/server-config.ts. Key environment variables:
| Variable | Description | Default |
|---|---|---|
OPENCHARGEMAP_API_KEY | Required. Open Charge Map API key, sent as the X-API-Key header. Free signup at openchargemap.org. | — |
OPENCHARGEMAP_BASE_URL | OCM API base URL. Override for a private mirror or testing. | https://api.openchargemap.io/v3 |
OPENCHARGEMAP_REFERENCE_REFRESH | When true, refresh reference data from the live /referencedata endpoint at startup, falling back to the bundled snapshot on failure. When false, stay fully offline on the bundled snapshot. | false |
MCP_TRANSPORT_TYPE | Transport: stdio or http. | stdio |
MCP_HTTP_PORT | Port for the HTTP server. | 3010 |
MCP_AUTH_MODE | Auth mode: none, jwt, or oauth. | none |
MCP_LOG_LEVEL | Log level (RFC 5424). | info |
LOGS_DIR | Directory for log files (Node.js only). | <project-root>/logs |
LOG_TOOL_FAILURE_PAYLOADS | Log each failed tool call's arguments and result, redacted by key name and capped at LOG_TOOL_FAILURE_PAYLOAD_MAX_BYTES (default 16384). A secret inside a free-form value is not redacted. | false |
STORAGE_PROVIDER_TYPE | Storage backend. | in-memory |
OTEL_ENABLED | Enable OpenTelemetry instrumentation (spans, metrics, completion logs). | false |
See .env.example for the full list of optional overrides.
Running the server
Local development
- Build and run:
# One-time build bun run rebuild # Run the built server bun run start:stdio # or bun run start:http - Run checks and tests:
bun run devcheck # Lint, format, typecheck, security, changelog sync bun run test # Vitest test suite bun run lint:mcp # Validate MCP definitions against spec
Docker
docker build -t openchargemap-mcp-server .
docker run --rm -e OPENCHARGEMAP_API_KEY=your-key -p 3010:3010 openchargemap-mcp-server
The Dockerfile defaults to HTTP transport, stateless session mode, and logs to /var/log/openchargemap-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.
Project structure
| Directory | Purpose |
|---|---|
src/index.ts | createApp() entry point — registers tools/resources and inits services. |
src/config | Server-specific environment variable parsing and validation with Zod. |
src/data | Bundled Open Charge Map reference snapshot (ocm-reference-data.ts) — the offline source for ID resolution. |
src/mcp-server/tools | Tool definitions (*.tool.ts) plus the shared station schema and renderers. |
src/mcp-server/resources | Resource definitions (*.resource.ts). |
src/services/openchargemap | OCM POI API client, response normalization, attribution, and the reliability-note helper. |
src/services/reference-data | Reference-data service — snapshot loading, lookup indices, curated aliases, optional live refresh. |
tests/ | Unit and integration tests mirroring src/. |
Development guide
See AGENTS.md (and CLAUDE.md) for development guidelines and architectural rules. The short version:
- Handlers throw, framework catches — no
try/catchin tool logic - Use
ctx.logfor request-scoped logging,ctx.statefor tenant-scoped storage - Register new tools and resources in the
createApp()arrays - Wrap external API calls: validate raw → normalize to domain type → return output schema; never fabricate missing fields
Attribution and data license
Charging-station, connector, and operator data is sourced from Open Charge Map, the community-maintained global registry of EV charging locations, and is licensed under **CC BY 4.0**.
Station data © Open Charge Map contributors, licensed under CC BY 4.0 (openchargemap.org).
Attribution is mandatory: every tool response carries this attribution string, and the server restates it in its session-level instructions. Any downstream use of the data must credit Open Charge Map and its contributors. This server's own code is Apache-2.0 (below); the license terms above apply to the data, not the software.
Contributing
Issues are welcome. Run checks and tests before submitting:
bun run devcheck
bun run test
License
Apache-2.0 — see LICENSE for details. Open Charge Map data carries its own license; see Attribution and data license.
Frequently asked questions
What is io.github.cyanheads/openchargemap-mcp-server?
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
How do I install io.github.cyanheads/openchargemap-mcp-server?
It runs as a remote server. In Claude Code: claude mcp add --transport http openchargemap-mcp-server 'https://openchargemap.caseyjhand.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.cyanheads/openchargemap-mcp-server need an API key?
Yes. It expects OPENCHARGEMAP_API_KEY, which you set in its configuration.
Is io.github.cyanheads/openchargemap-mcp-server open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains io.github.cyanheads/openchargemap-mcp-server?
It is published by cyanheads. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.