Kelvin MCP server¶
On this page you will learn what the Kelvin MCP server is and how it fits into the Kelvin Platform.
What the Kelvin MCP server is¶
The Kelvin MCP server is a bridge between MCP clients and the Kelvin API. It exposes the Kelvin API as MCP tools and proxies each tool call through to the real API using your authenticated session.
Compatible MCP clients include Claude, Cursor, and VS Code. This lets AI coding tools query assets, data streams, workloads, recommendations, and everything else exposed by the Kelvin API, without any custom integration work.
How it generates tools¶
The server reads the Kelvin API's OpenAPI specification on startup and turns each operation into an MCP tool automatically. The tool catalog mirrors the full Kelvin API surface and is regenerated from the spec rather than maintained by hand.
This means every capability available through the Kelvin API is immediately available to any connected AI coding tool.
Authentication model¶
The MCP server uses the same Keycloak-based authentication as the rest of the Kelvin Platform. Connecting a client opens a browser sign-in flow automatically — no manual token handling is needed.
Note
The MCP server grants no new permissions. It forwards your bearer token and the Kelvin API enforces your existing permissions. The assistant can only do what you can do.
Developer documentation¶
For setup and technical reference, see the Kelvin MCP developer documentation.