LogoLogo
Log in|Playground
  • Welcome
    • Introduction
    • FAQ
  • Capabilities
    • Log Management
    • Infrastructure Monitoring
    • Application Performance Monitoring (APM)
      • Application Metrics
      • Traces
      • Supported Technologies
    • Real User Monitoring (RUM)
  • Getting Started
    • Requirements
      • Kubernetes requirements
      • Kernel requirements for eBPF sensor
      • CPU architectures
      • ClickHouse resources
    • Installation & updating
    • Connect Linux hosts
    • Connect RUM
    • 5 quick steps to get you started
    • groundcover MCP
      • Configure groundcover's MCP Server
      • Getting-started Prompts
      • Real-world Use Cases
  • Use groundcover
    • Monitors
      • Create a new Monitor
      • Issues page
      • Monitor List page
      • Silences page
      • Monitor Catalog page
      • Monitor YAML structure
      • Embedded Grafana Alerts
        • Create a Grafana alert
    • Dashboards
      • Create a dashboard
      • Embedded Grafana Dashboards
        • Create a Grafana dashboard
        • Build alerts & dashboards with Grafana Terraform provider
        • Using groundcover datasources in a Self-hosted Grafana
    • Insights
    • Explore & Monitors query builder
    • Workflows
      • Create a new Workflow
      • Workflow Examples
      • Alert Structure
    • Search & Filter
    • Issues
    • Role-Based Access Control (RBAC)
    • Service Accounts
    • API Keys
    • APIs
    • Log Patterns
    • Drilldown
    • Scraping custom metrics
      • Operator based metrics
      • kube-state-metrics
      • cadvisor metrics
    • Backup & Restore Metrics
    • Metrics & Labels
    • Add custom environment labels
    • Configuring Pipelines
      • Writing Remap Transforms
      • Logs Pipeline Examples
      • Traces Pipeline Examples
      • Logs to Events Pipeline Examples
      • Logs/Traces Sensitive Data Obfuscation
      • Sensitive Data Obfuscation using OTTL
      • Log Filtering using OTTL
    • Querying your groundcover data
      • Query your logs
        • Example queries
        • Logs alerting
      • Query your metrics
      • Querying you data using an API
      • Using KEDA autoscaler with groundcover
  • Log Parsing with OpenTelemetry Pipelines
  • Log and Trace Correlation
  • RUM
  • Customization
    • Customize deployment
      • Agents in host network mode
      • API Key Secret
      • Argo CD
      • On-premise deployment
      • Quay.io registry
      • Configuring sensor deployment coverage
      • Enabling SSL Tracing in Java Applications
    • Customize usage
      • Filtering Kubernetes entities
      • Custom data retention
      • Sensitive data obfuscation
      • Custom storage
      • Custom logs collection
      • Custom labels and annotations
        • Enrich logs and traces with pod labels & annotations
        • Enrich metrics with node labels
      • Disable tracing for specific protocols
      • Tuning resources
      • Controlling the eBPF sampling mechanism
  • Integrations
    • Overview
    • Workflow Integrations
      • Slack Webhook Integration
      • Opsgenie Integration
      • Webhook Integration
        • Incident.io
      • PagerDuty Integration
      • Jira Webhook Integration
      • Send groundcover Alerts to Email via Zapier
    • Data sources
      • OpenTelemetry
        • Traces & Logs
        • Metrics
      • Istio
      • AWS
        • Ingest CloudWatch Metrics
        • Ingest CloudWatch Logs
        • Ingest Logs Stored on S3
        • Integrate CloudWatch Grafana Datasource
      • GCP
        • Ingest Google Cloud Monitoring Metrics
        • Stream Logs using Pub/Sub
        • Integrate Google Cloud Monitoring Grafana Datasource
      • Azure
        • Ingest Azure Monitor Metrics
      • DataDog
        • Traces
        • Metrics
      • FluentBit
      • Fluentd
      • JSON Logs
    • 3rd-party metrics
      • ActiveMQ
      • Aerospike
      • Cassandra
      • CloudFlare
      • Consul
      • CoreDNS
      • Etcd
      • HAProxy
      • Harbor
      • JMeter
      • K6
      • Loki
      • Nginx
      • Pi-hole
      • Postfix
      • RabbitMQ
      • Redpanda
      • SNMP
      • Solr
      • Tomcat
      • Traefik
      • Varnish
      • Vertica
      • Zabbix
    • Source control (Gitlab/Github)
  • Architecture
    • Overview
    • inCloud Managed
      • Setup inCloud Managed with AWS
        • AWS PrivateLink Setup
        • EKS add-on
      • Setup inCloud Managed with GCP
      • Setup inCloud Managed with Azure
      • High Availability
      • Disaster Recovery
      • Ingestion Endpoints
      • Deploying in Sensor-Only mode
    • Security considerations
      • Okta SSO - onboarding
    • Service endpoints inside the cluster
  • Product Updates
    • What's new?
    • Earlier updates
      • 2025
        • Mar 2025
        • Feb 2025
        • Jan 2025
      • 2024
        • Dec 2024
        • Nov 2024
        • Oct 2024
        • Sep 2024
        • Aug 2024
        • July 2024
        • May 2024
        • Apr 2024
        • Mar 2024
        • Feb 2024
        • Jan 2024
      • 2023
        • Dec 2023
        • Nov 2023
        • Oct 2023
Powered by GitBook
On this page
  • OAuth (recommended)
  • API Key
  • Have a Multi‑backend setup?
  • How to find your time zone
  • Client‑specific Guides
Export as PDF
  1. Getting Started
  2. groundcover MCP

Configure groundcover's MCP Server

Last updated 1 day ago

Set up your agent to talk to groundcover’s MCP server. Use OAuth for a quick login, or an API key for service accounts.

The MCP server supports two methods:

  • (Recommended for IDEs)

OAuth (recommended)

OAuth is the default if your agent supports it.

To get started, add the config below to your MCP client. Once you run it, your browser will open and prompt you to log in with your groundcover credentials.

🧘 Pro tip: You can copy a ready-to-go command from the UI. Go to the sidebar → Click your profile picture → "Connect to our MCP"

The tenant's UUID and your time zone will be auto-filled.

Configuration Example

{
  "mcpServers": {
    "groundcover": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.groundcover.com/api/mcp",
        "54278",
        "--header",
        "X-Timezone:<IANA_TIMEZONE>",
        "--header",
        "X-Tenant-Uuid:<TENANT_UUID>"
      ]
    }
  }
}

API Key

If your agent doesn’t support OAuth, or if you want to connect a service account, this is the way to go.

Prerequisites

Configuration Example

Parameters

  • AUTH_HEADER – your groundcover API key.

  • TIMEZONE – your time zone in IANA format.

{
  "mcpServers": {
    "groundcover": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.groundcover.com/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}",
        "--header", "X-Timezone:${TIMEZONE}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer <your_token>",
        "TIMEZONE": "<your_timezone>"
      }
    }
  }
}

Have a Multi‑backend setup?

If you're using a multi-backend setup (OAuth or API Key), just add the following header to the args list:

"--header", "X-Backend-Id:<BACKEND_ID>"

First, grab your backend ID (it’s basically the name):

  1. Open Data Explorer in groundcover.

  2. Click the Backend picker (top‑right) and copy the backend’s name.

How to find your time zone

OS
command

macOS

sudo systemsetup -gettimezone

Linux

timedatectl grep "Time zone"

Windows PowerShell

Get-TimeZone

Client‑specific Guides

Depending on your client, you can usually set up the MCP server through the UI - or just ask the client to add it for you. Here are quick links for common tools:

Service‑account API key – create one or use an existing API Key. Learn more at .

Your local time zone (IANA format, for example America/New_York or Asia/Jerusalem). See how to .

groundcover API keys
Instructions for Claude Desktop
Instructions for Claude Web
Instructions for Cursor
Instructions for Windsurf
Instructions for VS Code
find it below
OAuth
API Key