Integrations & AI
Open EVCCAT to modern AI workflows
Connect MCP clients so AI tools can interact with your platform context.
Key benefits
AI interoperability
Connect MCP-compatible AI tools to EVCCAT.
Platform context
Agents work with the CSMS reference instead of frozen exports.
API complement
Keep the API for the stack, MCP for AI workflows.
How it works
MCP integrations connect EVCCAT to AI assistants and tools compatible with the Model Context Protocol. They expose platform context to modern AI workflows. Teams want to query business tools with AI agents. MCP provides a suitable protocol, complementary to a classic REST API.
- 1
Enable MCP context
Prepare MCP access according to your configuration.
- 2
Connect the AI client
An MCP-compatible tool connects to EVCCAT.
- 3
Use in workflows
Query and use platform context from the AI tool.
In the EVCCAT platform
MCP clients connect to EVCCAT context so AI tools can access exposed information and capabilities within your access controls.
Use cases
External business assistant
An enterprise AI agent consults EVCCAT context via MCP.
Augmented ops workflow
Technical teams enrich their AI tooling with CSMS data.
Related features
FAQ
No. The assistant is built into the platform; MCP opens EVCCAT to compatible external AI tools.
API and MCP serve different uses and complement each other in the integration ecosystem.
See what EVCCAT can bring to your charging network
Talk with our team about your infrastructure, operations and monetization needs.