MCPO OpenAPI

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 AI Governance Platform stdio server and translates its tools into an HTTP surface.

MCPO is an adapter, not the preferred connection for VS Code, Cursor, or another MCP-aware AI client. Those clients should use native Streamable HTTP at http://localhost:8002/mcp, where they can discover and call MCP tools directly.

Start MCPO

./scripts/mcp/start-mcp.sh

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

Swagger UI

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

This is the only AI Governance Platform 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 ai-governance-mcpclient-credentials flow to call the REST control plane. Its service-account subject must be a AI Governance Platform tenant member with the required role assignments. This differs from native Streamable HTTP, which forwards each remote caller's token.

How this differs from native MCP

It is easy to confuse the two local ports. Use the following rule: if your client says it supports MCP, use port 8002; if it asks for a REST URL, Swagger page, or OpenAPI file, use port 8001.

I am using VS Code or an AI agent that supports MCP
  → http://localhost:8002/mcp

I am using Swagger, Postman, curl, an API gateway, or a generated SDK
  → http://localhost:8001/docs

The local launcher pins a compatible MCPO and MCP SDK pair so the proxy remains stable across MCP SDK major releases. Use the repository launcher instead of installing an unpinned mcpo command yourself.