一台为Komodo DevOps平台打造的Python MCP（模型上下文协议）服务器。直接通过像Claude这样的AI助手管理你的服务器、容器、堆栈、构建等等。

使用FastMCP、uvicorn和httpx构建。

快速入门（Docker Compose）

连接到MCP客户端

服务器在 / 处暴露一个可流式 HTTP 端点。

Claude 代码（CLI）：

Claude Desktop （claude_desktop_config.json）：

认证

服务器支持 OAuth 2.1，并支持基于浏览器的登录页面。启用 OAuth 后，MCP 客户端在收到访问令牌前会被重定向到登录表单。

启用OAuth

设置三个变量：

当OAuth处于激活状态时，服务器会暴露标准OAuth 2.1端点：

Komodo MCP Server

A Python MCP (Model Context Protocol) server for the Komodo DevOps platform. Manage your servers, containers, stacks, builds, and more — directly from AI assistants like Claude.

Built with FastMCP, uvicorn, and httpx.

Quick Start (Docker Compose)

services:
  komodo-mcp:
    image: ghcr.io/myrikld/komodo-mcp:latest
    ports:
      - "8000:8000"
    environment:
      - KOMODO_MCP_KOMODO_URL=https://your-komodo-instance.example.com
      - KOMODO_MCP_KOMODO_API_KEY=your_api_key
      - KOMODO_MCP_KOMODO_API_SECRET=your_api_secret
    restart: unless-stopped

docker compose up -d

Connect to MCP Client

The server exposes a Streamable HTTP endpoint at /.

Claude Code (CLI):

claude mcp add -s user --transport http komodo http://localhost:8000/

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "komodo": {
      "type": "http",
      "url": "http://localhost:8000/"
    }
  }
}

Authentication

The server supports OAuth 2.1 with a browser-based login page. When OAuth is enabled, MCP clients are redirected to a login form before receiving an access token.

Enabling OAuth

Set all three variables:

KOMODO_MCP_OAUTH_JWT_SECRET=
KOMODO_MCP_OAUTH_PASSWORD=
KOMODO_MCP_BASE_URL=https://mcp.example.com   # public URL of this server

When OAuth is active, the server exposes standard OAuth 2.1 endpoints:

Flow: MCP client → /authorize → browser opens /login → user enters password → client receives JWT access token (1h) + refresh token (30d).

Without OAuth configured, the server accepts all connections without authentication.

Restarts

The server keeps no session state, so restarting it does not log clients out — no volume required:

• Access and refresh tokens are self-contained JWTs, validated from their own signed claims.
• A registered client’s metadata is carried inside its client_id, which is itself a signed JWT.
• Everything is signed with a key derived from KOMODO_MCP_OAUTH_JWT_SECRET. Keep that secret stable: changing it invalidates all tokens and client registrations, forcing every client to authorize again.