Skip to content

io.github.cyanheads/openchargemap-mcp-server

by cyanheads · remote · local (npm) · no sign-in to list tools · v0.1.10 · published by GitHub user cyanheads

Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http openchargemap https://openchargemap.caseyjhand.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • openchargemap_find_stationsFind EV charging stations from the global Open Charge Map registry near a point or within a bounding box.No findings

    Why it is in this group

    • The name "openchargemap_find_stations" says "find": a word for reading.
    Description, as the server wrote it
    Find EV charging stations from the global Open Charge Map registry near a point or within a bounding box. Provide either a center (latitude + longitude + distance) or a boundingbox; optionally scope to a country with countrycode. This tool is coordinate-native and does not geocode place names — resolve a place like "Ballard, Seattle" to coordinates with openstreetmap_search_places first, then pass them here. Filter by connector type, minimum power (kW), operator/network, usage type (public/free/membership), charge level, operational status, and minimum charge points. Filter IDs are integers — resolve a connector or network name to its ID with openchargemap_lookup_reference (e.g. "CCS" -> 33). Each result includes title, address, distance from the search point, connections (type, power, count), operator, access rules, registry operational status, and the last-verified date. Results come back one page at a time: when a page reports truncated, repeat the same search with the reported nextOffset to read the next one.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • openchargemap_get_stationGet the full record for one Open Charge Map station by its numeric OCM ID.No findings

    Why it is in this group

    • The name "openchargemap_get_station" says "get": a word for reading.
    Description, as the server wrote it
    Get the full record for one Open Charge Map station by its numeric OCM ID. Returns every connection (type, level, power, current, quantity, per-connection status), the operator and network, usage and access restrictions (pay-at-location, membership, access key), the number of charge points, general comments, usage cost, the data provider, media, and verification recency. Set includeComments to also return community check-ins inline.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • openchargemap_get_station_commentsRead community check-ins and comments for one Open Charge Map station — the real-world reliability signal beyond the operator-reported registry status.No findings

    Why it is in this group

    • The name "openchargemap_get_station_comments" says "get": a word for reading.
    Description, as the server wrote it
    Read community check-ins and comments for one Open Charge Map station — the real-world reliability signal beyond the operator-reported registry status. Returns user comments and fault reports with ratings, dates, and the outcome the driver recorded ("Charged Successfully", "Failed to Charge (Equipment Not Operational)", …), alongside the station's current registry status and last-verified date, surfacing mismatches like "listed operational, but the last few check-ins report a fault." A busy station's check-ins come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • openchargemap_lookup_referenceResolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require.No findings

    Why it is in this group

    • The name "openchargemap_lookup_reference" says "lookup": a word for reading.
    Description, as the server wrote it
    Resolve Open Charge Map reference data to the integer IDs that openchargemap_find_stations filters require. Pick a category and pass a name or code to resolve — "CCS" or "Tesla Supercharger" -> a connectiontypeid, "ChargePoint" -> an operatorid, "Public - Pay At Location" -> a usagetypeid, "France" or "FR" -> a country. Omit the query to browse the whole category. Large categories come back one page at a time: when a page reports truncated, repeat the call with the reported nextOffset to read the next one.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.10. Values in angle brackets are yours to fill in.

claude mcp add --transport http openchargemap https://openchargemap.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__openchargemap__openchargemap_find_stations",
      "mcp__openchargemap__openchargemap_get_station",
      "mcp__openchargemap__openchargemap_lookup_reference",
      "mcp__openchargemap__openchargemap_get_station_comments"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as openchargemap. Review it before you use it.