openchargemap-mcp-server
Server Details
Find EV charging stations, detail, and reliability check-ins via the global Open Charge Map.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- cyanheads/openchargemap-mcp-server
- GitHub Stars
- 1
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.6/5 across 4 of 4 tools scored.
Each tool has a distinct, non-overlapping purpose: finding stations, getting station details, reading comments, and looking up reference IDs. No ambiguity between them.
All tools follow a consistent 'openchargemap_verb_noun' pattern (find_stations, get_station, get_station_comments, lookup_reference), making the naming predictable and easy to navigate.
With 4 tools, the server is well-scoped for its purpose: search, detail retrieval, community feedback, and reference lookup. Each tool earns its place without excess.
The tool set covers the core workflow for EV charging station information: finding stations, inspecting detailed records, reading community comments, and resolving reference data. No significant gaps are apparent.
Available Tools
4 toolsopenchargemap_find_stationsopenchargemap-mcp-server: find stationsRead-onlyInspect
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_geocode 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.
| Name | Required | Description | Default |
|---|---|---|---|
| levelid | No | Charge level ID (1=Low <2kW, 2=Medium >2kW, 3=High >40kW/fast). Array OR-matched. Use 3 as a coarse "fast charging only" filter when a specific connector is not required. | |
| distance | No | Search radius from the center point, in the unit given by distanceUnit (default km). Max 500. Keep small (5-25) for dense urban areas; widen for rural coverage. | |
| latitude | No | Center latitude (WGS84 decimal degrees). Use with longitude + distance for a radius search. Resolve place names via openstreetmap_geocode first. | |
| longitude | No | Center longitude (WGS84 decimal degrees). Use with latitude + distance for a radius search. | |
| maxresults | No | Maximum stations to return, ordered by distance from the search point. Max 200. | |
| minpowerkw | No | Minimum charging power in kW across any connection at the station. Use ~50 for DC fast charging, ~150 for high-power DC. Stations whose fastest connection is below this are excluded. | |
| operatorid | No | Operator/network ID, or array of IDs (OR-matched). Resolve a network name with openchargemap_lookup_reference (category "operators") — e.g. "Tesla", "ChargePoint". | |
| boundingbox | No | Bounding-box search as an alternative to a center+radius. Mutually exclusive with latitude/longitude/distance. | |
| countrycode | No | Restrict to one country by ISO 3166-1 alpha-2 code (e.g. "US", "FR", "GB"). Omit for a global search. The server is global by default — there is no implicit country. | |
| usagetypeid | No | Usage/access type ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "usagetypes") — e.g. Public=1, Public-Pay At Location=5, Public-Membership Required=4. | |
| distanceUnit | No | Unit for the distance parameter and the returned distance values. | KM |
| statustypeid | No | Registry operational-status ID, or array (OR-matched). Resolve via openchargemap_lookup_reference (category "statustypes"). NOTE: registry status is operator-reported and can be stale — combine with dateLastVerified and openchargemap_get_station_comments to judge real-world reliability, do not treat it as ground truth. | |
| minchargepoints | No | Minimum number of charge points (stalls) at the station. Filters out single-point locations when you need a station likely to have an open stall. | |
| connectiontypeid | No | Connector type ID, or an array of IDs (OR-matched). Resolve names with openchargemap_lookup_reference — e.g. CCS (Type 2)=33, CHAdeMO=2, NACS/Tesla Supercharger=27, Type 2 socket=25, Type 1/J1772=1. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The maxresults cap that was applied. |
| shown | No | Number of stations returned when the cap was hit. |
| stations | Yes | Matching stations, ordered by distance from the search point. |
| truncated | No | True when results were capped at maxresults. |
| totalCount | Yes | Number of stations returned. |
| attribution | Yes | Required attribution to Open Charge Map contributors under CC BY 4.0. |
| searchSummary | Yes | Human-readable echo of the resolved search: location mode, scope, and active filters as the server applied them. |
openchargemap_get_stationopenchargemap-mcp-server: get stationRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric OCM station ID (e.g. 145452). | |
| includeComments | No | Include community check-ins and comments inline in the response. Adds payload but gives the real-world reliability signal alongside the registry status. For comments alone, use openchargemap_get_station_comments. |
Output Schema
| Name | Required | Description |
|---|---|---|
| station | Yes | The full station record. |
| attribution | Yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| reliabilityNote | No | A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag. |
openchargemap_get_station_commentsopenchargemap-mcp-server: get station commentsRead-onlyIdempotentInspect
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 and dates, 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."
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric OCM station ID. | |
| maxresults | No | Maximum comments to return, newest first. Max 100. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The maxresults cap that was applied. |
| shown | No | Number of comments returned when the cap was hit. |
| notice | No | Guidance when the station has no check-ins on record. |
| comments | Yes | Community comments, newest first. Empty array means OCM has no check-ins for this station — absence of reports is not evidence the charger works. |
| stationId | Yes | OCM station ID the comments belong to. |
| truncated | No | True when comments were capped at maxresults. |
| totalCount | Yes | Number of comments returned. |
| attribution | Yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| stationTitle | Yes | Station name, for context. |
| isOperational | No | Whether the registry marks the station operational. Absent when the operational state is unknown. Compare against the comments below — they are the real-world check. |
| registryStatus | No | Current registry operational status (operator-reported). |
| reliabilityNote | No | A caveat when the registry status, verification age, coordinates, or comments suggest the listing may not reflect reality. Omitted when there is nothing to flag. |
| dateLastVerified | No | ISO 8601 date the listing was last verified. null when never verified. |
openchargemap_lookup_referenceopenchargemap-mcp-server: lookup referenceRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum entries to return when browsing or when a query matches several. Max 100. | |
| query | No | Name, title, code, or alias to resolve (e.g. "CCS", "CHAdeMO", "Tesla", "Public", "France", "FR"). Case-insensitive, matches on title, formal name, and known aliases. Omit to browse the entire category. | |
| category | Yes | Which reference set to query. connectiontypes -> connectiontypeid; operators -> operatorid; usagetypes -> usagetypeid; statustypes -> statustypeid; currenttypes -> current type; levels -> charge level (1/2/3); countries -> ISO country. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cap | No | The limit that was applied. |
| shown | No | Number of entries returned when the cap was hit. |
| notice | No | Guidance when a query matched nothing. |
| matches | Yes | Matching reference entries, best/exact match first. |
| category | Yes | The reference category queried. |
| truncated | No | True when a browse was capped at limit. |
| totalCount | Yes | Number of entries returned. |
| attribution | Yes | Required CC BY 4.0 attribution to Open Charge Map contributors. |
| filterParam | No | The find_stations input parameter these IDs feed (e.g. "connectiontypeid"). Omitted for categories with no direct filter (currenttypes; countries use countrycode). |
| snapshotDate | Yes | Date the bundled reference snapshot was captured, so callers know the data vintage. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!