Developers · power users

MCP Server API token

Model Context Protocol server — the Pipelet suite directly inside Claude, Cursor, Copilot.

Open API docs → Got questions? Get in touch

Free developer token on request with read-only access to a demo instance — just ask and we'll enable it.

Screenshot coming soon

The MCP Server makes the Pipelet suite directly usable for LLMs. When you work with Claude, Cursor or Copilot on an integration, the LLM can pull live data directly — charger status, session history, fleet configuration, energy prices.

Tool definitions are type-safe and scoped: a read-only token sees data, an admin token can additionally trigger config changes. Complete audit log of who made which tool call when.

Perfect for AI-assisted debugging, data exploration and rapid prototyping — the LLM knows the reality of your infrastructure, not just the documentation.

What to expect

✓

Type-safe tool definitions

Every tool has a strict JSON schema. The LLM cannot 'invent' parameters, errors are reported immediately instead of silently swallowed.

✓

Read-only & admin mode

Separate token scopes: read-only for exploration and analysis, admin for configuration changes. Claude never decides on admin calls alone.

✓

Audit trail

Every tool call is logged: token, time, tool name, parameters, result. Audit-ready for enterprise compliance.

✓

Every service reachable

OCPP logs, CPMS state, fleet config, energy prices, automation runs — every service in the suite is exposed as MCP tools.

Common scenarios

AI-assisted debugging

A driver reports an issue at charger XY-123. You ask Claude, Claude pulls the last hour of OCPP logs via MCP, diagnoses in seconds instead of hours.

Data exploration in the notebook

You want to know which tariffs are used most. Claude builds the queries via MCP, aggregates, plots — without you writing SQL.

How MCP Server fits into the suite

Integrates with

MCP Server https://developer.pipelet.com/mcp/

Driver Portal Home charging, charging history, CarData integra Fleet Portal Fleet management, driver management, RFID and bi CPMS Core The new operator UI: sites, charger commands, vo

Frequently asked questions

Is Pipelet available as source code?

Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.

Which OCPP versions are supported?

Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.

Can I use individual modules only?

Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.

What does onboarding look like?

We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.