v2.0.1

MCPO OpenAPI

Expose Kavach MCP tools through a conventional HTTP and OpenAPI-compatible surface.

When to use MCPO

Choose MCPO when the consumer understands HTTP/OpenAPI but does not implement MCP—for example Postman, a generated SDK, an API gateway, or an existing enterprise integration. MCPO launches the canonical Kavach stdio server and translates its tools into an HTTP surface.

Start MCPO

bash

./scripts/mcp/start-mcp.sh

The supported local workflow starts Keycloak and the REST control plane first. ./kavach-local.sh performs that setup and starts MCPO on port 8001.

Swagger UI

text

Swagger UI: http://127.0.0.1:8001/docs
OpenAPI:     http://127.0.0.1:8001/openapi.json

This is the only Kavach MCP variant with a Swagger/OpenAPI UI. Native Streamable HTTP uses MCP protocol messages instead; use MCP Inspector for its development browser UI.

Service identity

MCPO uses the configured kavach-mcpclient-credentials flow to call the REST control plane. Its service-account subject must be a Kavach tenant member with the required role assignments. This differs from native Streamable HTTP, which forwards each remote caller's token.