Coroot

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

9

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "jamesbrink-mcp-coroot": {
      "command": "uvx",
      "args": [
        "mcp-coroot"
      ],
      "env": {
        "COROOT_API_KEY": "YOUR_API_KEY",
        "COROOT_BASE_URL": "http://localhost:8080",
        "COROOT_PASSWORD": "your-password",
        "COROOT_USERNAME": "admin",
        "COROOT_SESSION_COOKIE": "SESSION_COOKIE_VALUE"
      }
    }
  }
}

This MCP Server integrates Coroot observability into your MCP client, letting you monitor applications, analyze performance, inspect logs and traces, and manage infrastructure through Coroot’s comprehensive API. It enables seamless interaction between your MCP client and Coroot to streamline monitoring, incident analysis, and governance across your systems.

How to use

You connect to Coroot by configuring an MCP server entry in your MCP client. Two common approaches are to run the server via your local CLI tool or to run it inside a container. Once connected, you can observe real-time application metrics, search and analyze logs, trace distributed requests, and manage dashboards, integrations, and incidents from your MCP client. Use the server to authenticate to Coroot with either a user/password pair or a session cookie for SSO/MFA. For data ingestion tasks, you may also provide an API key.

How to install

Prerequisites: you need a functioning MCP client runtime (the uvx CLI is used in examples here). Ensure you have network access to your Coroot instance and the credentials you will use for authentication.

Option 1: Install and run directly with the CLI. Install the MCP Coroot server package and start it through the MCP runtime.

Option 2: Use a container to run the MCP Coroot server. Provide the Coroot base URL and credentials as environment variables when launching the container.

Configuration and usage notes

Configure your MCP client with one or more coroot entries to connect to the server. The following configuration patterns are shown for running the server locally and via Docker, including both username/password authentication and session cookie authentication for SSO/MFA users.

Troubleshooting and security

If you encounter connectivity issues, verify that your Coroot instance is reachable at the configured base URL, test your network connectivity, and confirm that your credentials are correct. For authentication problems, remember that session cookies expire after periods of inactivity, and API keys are intended for data ingestion only. When using SSO/MFA, prefer session cookies and ensure you follow your organization’s security policies.

Available tools

get_current_user

Retrieve information about the currently authenticated user.

update_current_user

Update the profile of the currently authenticated user.

list_users

List all users in the Coroot context.

create_user

Create a new user in Coroot.

get_roles

Retrieve roles and permissions for users.

list_projects

List all accessible projects.

get_project

Get details of a specific project.

create_project

Create a new project in Coroot.

get_project_status

Check the health status of a project.

update_project_settings

Update project configuration settings.

delete_project

Delete a project.

list_api_keys

List API keys associated with the account.

create_api_key

Generate a new API key.

delete_api_key

Delete an API key.

get_application

Retrieve comprehensive metrics for an application.

get_application_logs

Search and analyze application logs.

get_application_traces

View distributed traces for requests across services.

get_applications_overview

Get a summary of all applications.

get_nodes_overview

Overview of infrastructure nodes and resources.

get_traces_overview

Summary of tracing activity.

get_deployments_overview

Overview of deployment history.

get_risks_overview

Overview of assessed risks.

list_dashboards

List all dashboards.

create_dashboard

Create a new dashboard.

get_dashboard

Get details of a dashboard.

update_dashboard

Update an existing dashboard.

delete_dashboard

Delete a dashboard.

list_integrations

List configured integrations.

configure_integration

Configure a new integration.

test_integration

Test connectivity for an integration.

delete_integration

Remove an integration from Coroot.

list_inspections

List available inspection types.

get_inspection_config

Retrieve inspection configuration.

update_inspection_config

Update inspection configuration.

get_application_categories

View application categories.

create_application_category

Create a new application category.

update_application_category

Update an existing category.

delete_application_category

Delete a category.

get_custom_applications

View custom applications defined in Coroot.

update_custom_applications

Define or modify custom applications.

automated_rca

Automatic root cause analysis for issues.

risk_assessment

Identify and track infrastructural and application risks.

deployment_tracking

Monitor deployments and their impact.

slo_management

Configure and track Service Level Objectives.

database_instrumentation

Instrument and monitor databases.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational