jamesbrink/mcp-coroot

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

16 stars 10 forks 品質 77 トレンド 29MIT

MCP server for Coroot observability platform - integrate monitoring, troubleshooting, and configuration tools with AI agents

概要

A Model Context Protocol server for Coroot. It lets an MCP client investigate a running system through Coroot: application health, logs, distributed traces, profiles, metrics, SLO incidents, alerts, deployments, costs and configuration. mcp-name: io.github.jamesbrink/mcp-coroot For single sign-on or multi-factor logins, where a password cannot be used, copy the coroot_session cookie out of a browser session instead: Check the configuration without starting a server: Username and password authentication is the best choice when it is available: the server logs in on demand and logs in again by itself when the session expires, which Coroot does after seven days. Carrying every tool costs context in every conversation before a single call, and most of the surface configures Coroot rather than investigating a running system. The default exposes the diagnose group only: 20 tools covering applications, nodes, logs, traces, profiles, metrics, incidents and alerts.

README

以下は原文 README の抜粋です。原文を見る。

MCP Server for Coroot

mcp-name: io.github.jamesbrink/mcp-coroot

Quick start

{
  "mcpServers": {
    "coroot": {
      "command": "uvx",
      "args": ["mcp-coroot"],
      "env": {
        "COROOT_BASE_URL": "http://localhost:8080",
        "COROOT_USERNAME": "admin",
        "COROOT_PASSWORD": "your-password"
      }
    }
  }
}

For single sign-on or multi-factor logins, where a password cannot be used, copy the coroot_session cookie out of a browser session instead:

{
  "mcpServers": {
    "coroot": {
      "command": "uvx",
      "args": ["mcp-coroot"],
      "env": {
        "COROOT_BASE_URL": "https://coroot.example.com",
        "COROOT_SESSION_COOKIE": "your-session-cookie"
      }
    }
  }
}

With Docker:

{
  "mcpServers": {
    "coroot": {
      "command": "docker",
      "args": ["run", "--rm", "-i",
               "-e", "COROOT_BASE_URL=http://host.docker.internal:8080",
               "-e", "COROOT_USERNAME=admin",
               "-e", "COROOT_PASSWORD=your-password",
               "jamesbrink/mcp-coroot:latest"]
    }
  }
}

Check the configuration without starting a server:

COROOT_BASE_URL=http://localhost:8080 uvx mcp-coroot --check

Configuration

Variable	Purpose
`COROOT_BASE_URL`	Coroot URL. Defaults to `http://localhost:8080`. `COROOT_URL` also works.
`COROOT_USERNAME`	Username for automatic login. Must be set with `COROOT_PASSWORD`.
`COROOT_PASSWORD`	Password for automatic login.
`COROOT_SESSION_COOKIE`	An existing `coroot_session` cookie, for SSO and MFA logins.
`COROOT_API_KEY`	Project API key. Coroot accepts it only on its Prometheus-compatible query endpoints, which no tool currently calls, so it cannot substitute for a login.
`COROOT_PROJECT`	Default project id, so tool calls can omit `project_id`.
`COROOT_TIMEOUT`	HTTP timeout in seconds. Defaults to 30.
`COROOT_VERIFY_SSL`	Set to `false` to skip TLS verification. Only for a self-signed certificate on a trusted network: it exposes the password and session cookie to anyone on the path.

GitHub で README 全文を見る

インストール

uvx mcp-coroot

MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "coroot": {
      "command": "uvx",
      "args": ["mcp-coroot"],
      "env": {
        "COROOT_BASE_URL": "http://localhost:8080",
        "COROOT_USERNAME": "admin",
        "COROOT_PASSWORD": "your-password"
      }
    }
  }
}