MMCPMarkets
JM

jamesbrink/mcp-coroot

Analytics & monitoring

Эта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал

16 stars 10 forks Качество 77 Тренд 29MIT
Repository Install

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

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

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.
Открыть полный README на GitHub

Установка

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" } } } }