Koma Gate MCP Server

What the code does

We read the source, 5 d ago · rules 995398eba69f

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

    const result = spawnSync(process.execPath, [live], { stdio: 'inherit' });

  const settingsPath = path.join(projectRoot, details.settingsRelativePath);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add koma-gate-mcp -- npx -y koma-gate-mcp

{
  "mcpServers": {
    "koma-gate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "koma-gate-mcp"
      ]
    }
  }
}

[mcp_servers.koma-gate-mcp]
command = "npx"
args = ["-y", "koma-gate-mcp"]

{
  "mcpServers": {
    "koma-gate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "koma-gate-mcp"
      ]
    }
  }
}

{
  "servers": {
    "koma-gate-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "koma-gate-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: KOMA_PROVIDER (LLM provider: openai, anthropic, google, deepseek, or ollama (default: google)), KOMA_MODEL (Optional model override for the selected provider), GEMINI_API_KEY (Google Gemini API key (used by the default provider)), OPENAI_API_KEY (OpenAI API key when KOMA_PROVIDER=openai), ANTHROPIC_API_KEY (Anthropic API key when KOMA_PROVIDER=anthropic), DEEPSEEK_API_KEY (DeepSeek API key when KOMA_PROVIDER=deepseek).