#MCP integration

k0smos exposes active-module tools through the Model Context Protocol at POST /api/mcp.

#Authentication

The endpoint requires MCP to be enabled, an authenticated user or personal API token with mcp.use, and any permission required by the individual tool.

#Transport

Use stateless Streamable HTTP with JSON-RPC 2.0. The server supports initialize, ping, tools/list, tools/call, and notifications/initialized.

#Connect a client

Configure the client with the tenant HTTPS endpoint and keep credentials in its secret store. Start with tools/list; the returned metadata describes inputs, outputs, safety annotations, and the tools exposed by active modules.

#Safe use

Review tool permissions before automation, use a least-privilege token, and keep human approval around destructive or financially significant actions.