Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Operate a network of EV charge points over OCPP: status, sessions, tariffs, prices, remote commands
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
Authorization비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
터미널에서 이 명령어를 실행하세요
claude mcp add --transport http askacharge https://askacharge.com/askacharge/api/mcp --header 'Authorization: your-value'실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"askacharge": {
"url": "https://askacharge.com/askacharge/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"askacharge": {
"type": "http",
"url": "https://askacharge.com/askacharge/api/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
Authorization 비밀 필수 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
아직 이 서버의 도구 목록을 읽지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 askacharge.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트는 차례대로 돌아가며 점검해요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: Authorization
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 2개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, FOGA node
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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.
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.
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.
Read
| Tool | What it answers |
|---|---|
askacharge_listar_cargadores | Every charge point with OCPP status, location and last contact |
askacharge_ver_cargador | One charger in detail: connectors, power, access mode, status |
askacharge_estado_en_vivo | Right now: chargers connected, sessions running, power being drawn |
askacharge_resumen | Period KPIs — energy, revenue, net margin, sessions, customers |
askacharge_listar_sesiones | Charging session history with energy, revenue and cost |
askacharge_listar_incidencias | Open faults per charger |
askacharge_listar_tarifas | Tariff groups: per kWh, per hour, per session, PVPC or free |
askacharge_precio_pvpc_hoy | Today's hour-by-hour Spanish PVPC electricity price |
askacharge_listar_clientes | Fleet customers with their tariff and monthly consumption |
askacharge_limites_de_potencia | kW ceiling per location and load-balancing strategy |
askacharge_traza_de_actividad | What the brand's API keys did: writes and rejected attempts |
askacharge_estado_comando | How 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).
| Tool | What it does |
|---|---|
askacharge_arrancar_carga | Remote start (OCPP RemoteStartTransaction) |
askacharge_parar_carga | Remote stop (OCPP RemoteStopTransaction) — cuts a live session |
askacharge_reiniciar_cargador | Reboot, soft or hard (OCPP Reset) |
askacharge_cambiar_disponibilidad | Put a charger in or out of service (OCPP ChangeAvailability) |
askacharge_desbloquear_conector | Release a stuck cable (OCPP UnlockConnector) |
askacharge_refrescar_estado | Ask the charger to send its status/heartbeat/meter now (OCPP TriggerMessage) |
askacharge_diagnosticos | Ask the charger to upload its diagnostics file (OCPP GetDiagnostics) |
Write
| Tool | What it does |
|---|---|
askacharge_crear_cargador | Register a charge point |
askacharge_cargadores_simulados | Sandbox: add up to 10 simulated OCPP chargers that connect within a minute and answer every command |
askacharge_crear_tarifa | Create a tariff group (per_kwh, per_hour, per_session, pvpc_margin, free…) |
askacharge_crear_cliente | Register a fleet customer |
askacharge_crear_tag_rfid | Authorise an RFID tag on the brand |
Escape hatch
| Tool | What it does |
|---|---|
askacharge_llamar_api | Call any of the platform's 463 API operations, under the same permission checks |
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.
claude mcp add --transport http askacharge https://askacharge.com/askacharge/api/mcp \
--header "Authorization: Bearer ask_live_..."
{
"mcpServers": { "askacharge": { "type": "http", "url": "https://askacharge.com/askacharge/api/mcp", "headers": { "Authorization": "Bearer ask_live_..." } } } }
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.
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.
A fuller statement of what the platform is and is not — including current architectural limits — lives at askacharge.com/llms.txt.
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.
MIT — see LICENSE.
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"