OCPPLab developer docs | OCPPLab Docs

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.

Using a coding agent? npx skills add ev-cloudx/ocpplab-skills teaches Claude Code, Codex, Cursor and other agents how to use OCPPLab. See Agent skills.

Start here

Get a token

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

Bring two chargers online

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

Charge

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

What the API covers

Domain	What you can do
`evcharger`	Deploy virtual chargers, send them OCPP commands, read their logs, browse the charger catalog
`cpo`	Manage your charge points, EVSEs, connectors, locations, tariffs, sessions and CDRs
`emsp`	Manage driver tokens, token groups, partner location networks and roaming identities
`ocpi`	Register OCPI partners, run the credentials handshake, push and pull roaming data
`proxy`	Route OCPP and OCPI traffic through OCPPLab and send commands through it
`booking`	Offer bookable locations and move bookings from reserved to fulfilled
`energy`	Set power limits on chargers and read their power measurements
`webhook`	Receive 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.