原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Openchargemap MCP Server

作者:cyanheads版本 0.2.0i★ 2i电脑或云端官方网站 ↗
注册名称io.github.cyanheads/openchargemap-mcp-server

安装方法

What it does

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

  • Connects 电脑或云端
  • Account or key Cloud: No key needed · Local: Needs OPENCHARGEMAP_API_KEY
  • Category 旅行、地图与天气

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度6/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分26/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 Openchargemap MCP Server。按照 https://mcp.popnx.com/i/cyanheads-openchargemap-mcp-server.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(openchargemap.caseyjhand.com) · ✓ 命令已检查 2026年11月14日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Openchargemap MCP Server
    Remote MCP server URL · 地址https://openchargemap.caseyjhand.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsOpenchargemap MCP Server

  4. 试一试

    用 Openchargemap MCP Server 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Openchargemap MCP Server,或回答中出现 Openchargemap MCP Server 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Openchargemap MCP Server
    Connection · 地址https://openchargemap.caseyjhand.com/mcp
  3. 在聊天中选择 Openchargemap MCP Server

    开启新聊天,输入前先从插件列表中选择 Openchargemap MCP Server

  4. 试一试

    用 Openchargemap MCP Server 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Openchargemap MCP Server,或回答中出现 Openchargemap MCP Server 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user openchargemap https://openchargemap.caseyjhand.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Openchargemap MCP Server 在列表中并显示已连接

  4. 试一试

    用 Openchargemap MCP Server 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Openchargemap MCP Server,或回答中出现 Openchargemap MCP Server 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Openchargemap MCP Server 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Openchargemap MCP Server,或回答中出现 Openchargemap MCP Server 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Openchargemap MCP Server 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Openchargemap MCP Server,或回答中出现 Openchargemap MCP Server 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://openchargemap.caseyjhand.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Openchargemap MCP Server 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

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

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "openchargemap": {
      "url": "https://openchargemap.caseyjhand.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "openchargemap": {
      "type": "http",
      "url": "https://openchargemap.caseyjhand.com/mcp"
    }
  }
}

安装在电脑上

Claude Code

claude mcp add --scope user openchargemap --env OPENCHARGEMAP_API_KEY=your-value -- npx -y @cyanheads/openchargemap-mcp-server

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "openchargemap": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/openchargemap-mcp-server"
      ],
      "env": {
        "OPENCHARGEMAP_API_KEY": "your-value"
      }
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "openchargemap": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/openchargemap-mcp-server"
      ],
      "env": {
        "OPENCHARGEMAP_API_KEY": "your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "openchargemap": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/openchargemap-mcp-server"
      ],
      "env": {
        "OPENCHARGEMAP_API_KEY": "your-value"
      }
    }
  }
}

需要你填写的值

  • OPENCHARGEMAP_CLAMP_LIMITS env
    将过大的正整数页面大小限制为工具的最大值;false 则恢复为拒绝。
    查看英文原文Clamp oversized positive integer page sizes to the tool maximum; false restores rejection.
  • OPENCHARGEMAP_API_KEY 机密 必填 env
    Open Charge Map API 密钥,在每个请求中作为 X-API-Key 请求头发送。可在 openchargemap.org 免费即时注册。
    查看英文原文Open Charge Map API key, sent as the X-API-Key header on every request. Free instant signup at openchargemap.org.
  • OPENCHARGEMAP_BASE_URL env
    覆盖 OCM API 基础 URL(默认 https://api.openchargemap.io/v3)。用于私有镜像或测试。
    查看英文原文Override the OCM API base URL (default https://api.openchargemap.io/v3). For a private mirror or testing.
  • OPENCHARGEMAP_REFERENCE_REFRESH env
    为 true 时,启动时从实时 /referencedata 端点刷新参考数据,失败时回退到内置快照。
    查看英文原文When true, refresh reference data from the live /referencedata endpoint at startup, falling back to the bundled snapshot on failure.
  • MCP_LOG_LEVEL env
    设置输出的最低日志级别(例如 'debug'、'info'、'warn')
    查看英文原文Sets the minimum log level for output (e.g., 'debug', 'info', 'warn').

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
115/周
许可证i
Apache-2.0
连接方式
电脑或云端
传输方式
stdio, streamable-http
最新版本i
0.2.0
发布到注册中心i
2026年10月26日
代码最后更新i
2026年10月26日
最近检查
2026年11月17日
作者
cyanheads
软件包
npm: @cyanheads/openchargemap-mcp-server
npm: @cyanheads/openchargemap-mcp-server
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

在你的电脑上运行,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • openchargemap_find_stations

    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 geocod

  • openchargemap_get_station

    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 cha

  • openchargemap_lookup_reference

    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 us

  • openchargemap_get_station_comments

    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", "Faile

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月18日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 cyanheads 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于23天前

  • ✓ 通过

    有许可证

    使用 Apache-2.0

  • ✓ 通过

    端点有响应

    在 568 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 4 个工具描述,未发现针对 AI 的隐藏指令

已公开的漏洞(OSV.dev)

OSV.dev 中没有 @cyanheads/openchargemap-mcp-server@0.2.0 的记录

只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/cyanheads-openchargemap-mcp-server.svg)](https://mcp.popnx.com/en/servers/cyanheads-openchargemap-mcp-server)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“旅行、地图与天气”中的其他服务器比较i

  • 星标数多于此分类中其他 1998 个服务器的 92%
  • 发布到注册中心的时间比此分类中其他 1998 个服务器的 56% 更新
  • 基础检查结果等于或优于此分类中其他 1998 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Openchargemap MCP Server 安全吗?

它在 5 项适用的基础检查中通过了 5 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:OPENCHARGEMAP_API_KEY

它在我的电脑上运行还是在云端?

两种方式都可以:安装在你的电脑上,或者连接云端版本。

它还在维护吗?

GitHub 仓库最后更新于23天前,最新版本(0.2.0)于23天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Mu, Award Travel Finder, Killbottleneck, Whimsical, HasData Google Maps

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Mu

News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.

作者:micro正在增长★ 4404个月前更新

在云端运行✓ micro.mu

Killbottleneck

Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.

作者:tengolabs起步阶段↓ 328/周★ 1411天前更新

在你的电脑上运行✓ 服务方 · killbottleneck.com

Whimsical

Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.

作者:WhimsicalCode起步阶段★ 112个月前更新

在云端运行✓ 服务方 · whimsical.com

HasData Google Maps

Google Maps places, reviews, contributor history, photos and posts as JSON. No Google Cloud.

作者:HasData起步阶段↓ 107/周★ 102个月前更新

电脑或云端✓ 服务方 · hasdata.com
与相似项目对比
本项
Openchargemap MCP Server
MuAward Travel FinderKillbottleneckWhimsicalHasData Google Maps
运行位置云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装需要安装在电脑上在云端运行,无需安装云端或安装在电脑上都可以
需要密钥是否否是否是
可在 Claude 中按 + 添加否否否否是否
基础检查5/54/43/33/34/45/5
许可证Apache-2.0AGPL-3.0MITMITMITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

@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 • 2 Resources

Public Hosted Server: https://openchargemap.caseyjhand.com/mcp


Overview

EV charging stations worldwide from Open Charge Map. Search by location, connector, and network, pull full station detail, and read community check-ins on whether a charger actually works.

Tools
ToolDescription
openchargemap_find_stationsFind charging stations near a point or within a bounding box, filtered by connector, power, network, usage, status, and charge points. Coordinate-native.
openchargemap_get_stationFull record for one station by numeric OCM ID — every connection, operator, access rules, charge points, cost, media, and a computed reliability note.
openchargemap_lookup_referenceResolve 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_commentsCommunity check-ins for one station alongside the registry status and last-verified date, so registry-vs-reality mismatch is visible.
Resources
ResourceDescription
openchargemap://station/{id}Full station record (with community comments) by numeric OCM ID — the URI-addressable twin of openchargemap_get_station.
skill://openchargemap-guide/SKILL.mdGuide to recommending compatible, accessible chargers, assessing reliability evidence, and checking search coverage. Also ships with plugin, npm, Docker, and MCPB installs.

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, distanceUnit KM or Miles, max 500) or boundingbox — exactly one mode per call; optional countrycode (ISO 3166-1 alpha-2) and filters connectiontypeid, minpowerkw, operatorid, usagetypeid, levelid, statustypeid, minchargepoints (the ID filters take one integer ID or an OR-matched array, resolved via openchargemap_lookup_reference)
  • maxresults caps the page (default 25, max 200) and offset pages through a fixed cached pool of up to 500 candidates per search. A 501st record only detects an upstream remainder: totalCount is exact without that sentinel and a floor when it is present; the notice says which
  • No matches returns a successful empty list with search recovery guidance. Unknown country codes are not applied and are disclosed in the summary and notice. Fails with invalid_location (no search area, half a center, or a coordinate beside a boundingbox), auth_failed, or upstream_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, and dateLastVerified; includeComments adds every check-in inline, unpaged (use openchargemap_get_station_comments for a heavily-commented station)
  • reliabilityNote is 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 with not_found, auth_failed, or upstream_unavailable

openchargemap_lookup_reference tool
  • category (connectiontypes, operators, usagetypes, statustypes, currenttypes, levels, countries) plus an optional case-insensitive query naming a title, code, or alias ("CCS", "Tesla Supercharger", "FR"); omit query to browse the category (limit max 100, default 25, paged via offset/nextOffset)
  • Returns the matching id(s), the filterParam they feed into openchargemap_find_stations, and source (live or bundled) with a snapshotDate — answered offline from the bundled snapshot unless OPENCHARGEMAP_REFERENCE_REFRESH refreshed it at startup. A miss returns a successful empty list with spelling/browse guidance

openchargemap_get_station_comments tool
  • Check-ins for one station by numeric OCM id, newest first, each with rating, date, and recorded outcome — maxresults caps the page (default 25, max 100), paged via offset/nextOffset; totalComments counts the station's whole set, and reliabilityNote's fault ratio is computed over all of it
  • Returns the registry status, isOperational, and dateLastVerified beside the comments; an empty comments: [] is not an error (no reports is not evidence the charger works); fails with not_found, auth_failed, or upstream_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_found when 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 /referencedata call, 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 openstreetmap server's openstreetmap_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, and dateLastVerified on every station, plus a plain-prose reliabilityNote derived 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
  • Attribution to Open Charge Map contributors and station data providers on every response; per-station provider license terms and open-data flags when supplied

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-Key header on every request; the server fails fast at startup if it's unset.
Installation
  1. Clone the repository:
git clone https://github.com/cyanheads/openchargemap-mcp-server.git
  1. Navigate into the directory:
cd openchargemap-mcp-server
  1. Install dependencies:
bun install
  1. 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 environme

只显示了开头部分;其余内容请在仓库中阅读