原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

askacharge.com — EV charging network

作者:javierojan版本 1.0.0i★ –i在云端运行
注册名称com.askacharge/askacharge

安装

概览

作者提供的说明(英文原文)

Operate a network of EV charge points over OCPP: status, sessions, tariffs, prices, remote commands

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在云端运行
  • 传输方式: Streamable HTTP
  • 分类: 其他
  • 你需要填写:Authorization

安装

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

安装之前

标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

在终端中运行这条命令

claude mcp add --transport http askacharge https://askacharge.com/askacharge/api/mcp --header 'Authorization: your-value'

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "askacharge": {
      "url": "https://askacharge.com/askacharge/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "askacharge": {
      "type": "http",
      "url": "https://askacharge.com/askacharge/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • Authorization 机密 必填 HTTP header
    Bearer . Created by the brand in its panel, under API keys. The key's scopes decide which tools are listed and which calls are allowed.

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

它能做什么

我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 askacharge.com 验证(注册中心会核实域名所有权)

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    端点有响应

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    使用 OAuth 登录

    尚未检查;我们会轮流检查各个端点

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

与“其他”中的其他服务器比较i

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

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

常见问题

askacharge.com — EV charging network 安全吗?

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

它需要哪些密钥或代码?

你需要填写:Authorization

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

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.0.0)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, debuff

替代选择

同一分类中其他作者的服务器,按星标数排序。

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

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

debuff

作者:debuffjp

Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.

在你的电脑上运行今天更新
安装

作者的 README

打开 README

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

askacharge.com MCP server

Let an AI agent operate a network of EV charge points.

askacharge.com is a CSMS — a Charging Station Management System — for electric vehicle charging: OCPP 1.6J and 2.0.1 to the hardware, tariffs and billing, QR and RFID driver payments, OCPI 2.2 roaming between operators, and fiscal invoicing. This repository documents its remote MCP server, which exposes that platform to any Model Context Protocol client.

Nothing to install. It is a hosted endpoint:

https://askacharge.com/askacharge/api/mcp

Transport is JSON-RPC 2.0 over HTTP POST (streamable-http). Protocol versions accepted: 2025-06-18, 2025-03-26, 2024-11-05. GET returns 405 on purpose — there is no SSE stream.


Why this exists

Charge point operators spend their day on questions an agent can answer directly: *which chargers are offline right now, what did site X earn last month, is it cheap enough to charge at this hour, reboot the one that stopped responding.* The REST API has always been able to do that. MCP is what makes it usable by an agent without anyone writing an integration first — the value is not the protocol, it is the description of when to use each tool and what happens if you get it wrong.

Authentication

One header, the brand's API key, created from the panel under *API keys*:

Authorization: Bearer ask_live_...

X-Api-Key: ask_live_... works too.

Once a key is present, its scopes decide which tools you can see. A read-only key never gets shown askacharge_parar_carga. Commands can be granted one by one: a key with commands:remote-start and commands:remote-stop sees start and stop but not reboot (commands:reset) or firmware; commands:write still means all of them. A key restricted to one location (commands:reset@hotel-madrid) sees the command tools and receives a 403 when it aims them at a charger somewhere else. A key belongs to one brand and reaches only that brand's data.

The 25 tools

Read

ToolWhat it answers
askacharge_listar_cargadoresEvery charge point with OCPP status, location and last contact
askacharge_ver_cargadorOne charger in detail: connectors, power, access mode, status
askacharge_estado_en_vivoRight now: chargers connected, sessions running, power being drawn
askacharge_resumenPeriod KPIs — energy, revenue, net margin, sessions, customers
askacharge_listar_sesionesCharging session history with energy, revenue and cost
askacharge_listar_incidenciasOpen faults per charger
askacharge_listar_tarifasTariff groups: per kWh, per hour, per session, PVPC or free
askacharge_precio_pvpc_hoyToday's hour-by-hour Spanish PVPC electricity price
askacharge_listar_clientesFleet customers with their tariff and monthly consumption
askacharge_limites_de_potenciakW ceiling per location and load-balancing strategy
askacharge_traza_de_actividadWhat the brand's API keys did: writes and rejected attempts
askacharge_estado_comandoHow a launched command is going, by its job_id: acked (charger accepted, waiting for the real effect), confirmed (the effect arrived — a session started, the charger came back after a reset), timeout, rejected, failed

OCPP commands — these act on physical hardware. Each one returns the charger's acknowledgement inline plus a `job_id`; the real effect arrives later over OCPP and closes the job, so ask askacharge_estado_comando instead of repeating the command (repeating it starts two sessions or reboots twice).

ToolWhat it does
askacharge_arrancar_cargaRemote start (OCPP RemoteStartTransaction)
askacharge_parar_cargaRemote stop (OCPP RemoteStopTransaction) — cuts a live session
askacharge_reiniciar_cargadorReboot, soft or hard (OCPP Reset)
askacharge_cambiar_disponibilidadPut a charger in or out of service (OCPP ChangeAvailability)
askacharge_desbloquear_conectorRelease a stuck cable (OCPP UnlockConnector)
askacharge_refrescar_estadoAsk the charger to send its status/heartbeat/meter now (OCPP TriggerMessage)
askacharge_diagnosticosAsk the charger to upload its diagnostics file (OCPP GetDiagnostics)

Write

ToolWhat it does
askacharge_crear_cargadorRegister a charge point
askacharge_cargadores_simuladosSandbox: add up to 10 simulated OCPP chargers that connect within a minute and answer every command
askacharge_crear_tarifaCreate a tariff group (per_kwh, per_hour, per_session, pvpc_margin, free…)
askacharge_crear_clienteRegister a fleet customer
askacharge_crear_tag_rfidAuthorise an RFID tag on the brand

Escape hatch

ToolWhat it does
askacharge_llamar_apiCall any of the platform's 463 API operations, under the same permission checks

It does not reimplement the product

Every tool runs against askacharge.com's own REST API with the same key, so it passes through the same scopes, the same audit trail, the same rate limit and the same idempotency handling. If a tool could ever do something the API forbids, that is a bug in the server, not a feature. The envelope itself is not what gets logged — the concrete operation it triggered is.

Using it

Claude Code
claude mcp add --transport http askacharge https://askacharge.com/askacharge/api/mcp \

--header "Authorization: Bearer ask_live_..."

Clients that take a JSON config
{

"mcpServers": { "askacharge": { "type": "http", "url": "https://askacharge.com/askacharge/api/mcp", "headers": { "Authorization": "Bearer ask_live_..." } } } }

Raw, to check it is alive
curl -s -X POST https://askacharge.com/askacharge/api/mcp \

-H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

No key needed for that: initialize, ping and tools/list answer anonymously, and the anonymous tools/list returns the whole catalogue of 25 tools (it is public anyway — it is the table above). Everything else — tools/call — needs the key, and without one you get a JSON-RPC error (-32001) saying so. A key that is present but invalid is an error too, not a fallback to anonymous.

Getting a key

Create an account at askacharge.com — 30-day trial, no card — then *API keys* in the panel. Pricing is a flat €20/month with unlimited chargers and no software commission per session; the whole list, including what does carry a percentage, is at askacharge.com/askacharge/en/pricing.html.

Honest limits

  • Tool names and descriptions are in Spanish. The platform's first market is Spain and the Basque Country. Models handle it without trouble, but you should know before you wire it in.
  • Scoping a key by location restricts what it can act on, not what it can read. A listing still returns the whole brand. This is documented behaviour, not an oversight.
  • There is no separate sandbox. To try things without consequences, create a brand in trial mode.
  • No SSE stream. Request/response only.

A fuller statement of what the platform is and is not — including current architectural limits — lives at askacharge.com/llms.txt.

Related


En español

Servidor MCP remoto de askacharge.com, la plataforma de gestión de cargadores de vehículo eléctrico (CSMS) con OCPP 1.6J/2.0.1, roaming OCPI 2.2, pago por QR y facturación fiscal (Verifactu y TicketBAI/Batuz).

Endpoint: https://askacharge.com/askacharge/api/mcp. No hay nada que instalar. Se autentica con la API key de la marca en Authorization: Bearer, y los scopes de esa key deciden qué herramientas se ven: una key de solo lectura nunca ve las de parar una carga, los comandos se pueden conceder uno a uno (commands:remote-start sin commands:reset), y una acotada por ubicación (commands:reset@hotel-madrid) recibe un 403 si apunta a un cargador de otra sede. Cada comando devuelve un job_id y askacharge_estado_comando dice si el efecto real llegó.

Son 25 herramientas —cargadores, estado en vivo, sesiones, tarifas, PVPC, clientes, límites de potencia, comandos OCPP y altas— más askacharge_llamar_api, que abre las 463 operaciones de la API con el mismo control de permisos. Ninguna reimplementa lógica de negocio: todas se ejecutan contra la propia API REST, con los mismos scopes, la misma traza y el mismo límite de uso.

Cuenta y key: askacharge.com, 30 días de prueba sin tarjeta. Precios en askacharge.com/askacharge/precios.html.

License

MIT — see LICENSE.

Registry

Published in the official MCP Registry as com.askacharge/askacharge, authenticated against the askacharge.com domain.

curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=askacharge"

See also

问 PopNx