Skip to navigation

OCPPLab developer docs

Drive virtual EV chargers, your CPO and eMSP data, and OCPI roaming from code, the terminal, or an AI agent.

OCPPLab gives you one API for EV charging work: virtual chargers that speak OCPP to your CSMS, your charging infrastructure as a CPO, driver tokens as an eMSP, OCPI roaming with partners, bookings, energy limits and webhooks.

Pick the way you want to call it:

TypeScript SDK

npm i ocpplab. Typed client for Node.js and the browser.

Python SDK

pip install ocpplab. Sync and async clients.

CLI

ocpplab-cli: one command per API operation, with browser sign-in.

MCP

Connect Claude, Cursor, VS Code or ChatGPT to 288 OCPPLab tools.

Start here

1

Get a token

In Studio, open Settings → SDK tokens and select Generate token. See Authentication.

2

Bring two chargers online

Follow the Quickstart: it deploys two virtual chargers against your CSMS and waits until both connect.

3

Charge

Plug a connector in, start a session and stop it with Plug, charge and unplug.

What the API covers

DomainWhat you can do
evchargerDeploy virtual chargers, send them OCPP commands, read their logs, browse the charger catalog
cpoManage your charge points, EVSEs, connectors, locations, tariffs, sessions and CDRs
emspManage driver tokens, token groups, partner location networks and roaming identities
ocpiRegister OCPI partners, run the credentials handshake, push and pull roaming data
proxyRoute OCPP and OCPI traffic through OCPPLab and send commands through it
bookingOffer bookable locations and move bookings from reserved to fulfilled
energySet power limits on chargers and read their power measurements
webhookReceive events on your HTTPS endpoints

Each domain is a namespace in the SDKs (client.cpo...), a command group in the CLI and its own MCP server. See Concepts.

Looking for OCPP or OCPI protocol references? They live at ocpplab.com/docs.