KloudMate MCP Server

The KloudMate MCP server lets your AI coding tools and agents pull observability data straight from your workspace. Point a client like Claude Code, Cursor, or VS Code at it, and you can ask about errors, latency, traces, and firing alerts in plain language, without leaving your editor or opening the KloudMate UI.

This is the mirror image of the MCP integrations you connect into the Assistant. There, KloudMate is the client calling out to other tools. Here, KloudMate is the server, and your agent is the client calling in. The connection is built on the Model Context Protocol, an open standard for giving language models access to external tools and data.

After you connect, your agent can chain KloudMate’s query tools to investigate an incident, answer a question about a service, or run a repeatable workflow you’ve defined.

Connection details

The server is a single remote endpoint. You authenticate with a KloudMate Personal API Key passed as a bearer token, and set the workspace you want to read in an x-workspace-id header.

Setting	Value
Endpoint	`https://api.kloudmate.com/mcp`
Transport	Streamable HTTP
Authentication	`Authorization: Bearer YOUR_API_KEY`
Workspace	`x-workspace-id: YOUR_WORKSPACE_ID`

A personal key carries your access to every workspace you belong to, so the connection needs the x-workspace-id header to know which one to read. Find the workspace ID in the workspace’s URL in the KloudMate app. To point the same key at a different workspace, change that header. One key works for all of them.

Before you start

You’ll need:

A KloudMate Personal API Key. From the account menu (top-right), open API keys and click Create Key. It’s tied to your account and reads whatever you can read. Copy it when it’s shown (it’s shown only once) and keep it handy for your client’s config. Any signed-in user can create one; you don’t need the Developer role. See API Keys for the full walkthrough.
The workspace ID you want to query. Find it in the workspace’s URL in the KloudMate app; it goes in the x-workspace-id header.
An MCP-capable client. Any tool that supports remote MCP servers over Streamable HTTP with custom headers works. The steps below cover Claude Code, Cursor, VS Code, and Claude Desktop.

Connect your client

Pick your tool and follow the steps. Swap YOUR_API_KEY for the key you just created, and YOUR_WORKSPACE_ID for the workspace you want to query.

Add the server from your terminal with the claude mcp add command:

claude mcp add --transport http kloudmate https://api.kloudmate.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "x-workspace-id: YOUR_WORKSPACE_ID"

By default the server is available in the current project only. Add --scope user before the server name to make it available across all your projects:

claude mcp add --transport http --scope user kloudmate https://api.kloudmate.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "x-workspace-id: YOUR_WORKSPACE_ID"

Run /mcp inside Claude Code to confirm kloudmate shows as connected and to see the tools it exposes.

Create or edit ~/.cursor/mcp.json (global, all projects) or .cursor/mcp.json (this project only), and add the server:

{
  "mcpServers": {
    "kloudmate": {
      "url": "https://api.kloudmate.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:KLOUDMATE_API_KEY}",
        "x-workspace-id": "YOUR_WORKSPACE_ID"
      }
    }
  }
}

The ${env:KLOUDMATE_API_KEY} reference reads the key from your environment so it never lands in the file. Set KLOUDMATE_API_KEY in your shell, then open Cursor Settings → MCP to confirm kloudmate connects. You can also paste the key directly in place of the reference, but keep that file out of any repository.

Create .vscode/mcp.json in your workspace. The inputs block prompts you for the key the first time the server starts and stores it securely, so the key stays out of the file:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "kloudmate-api-key",
      "description": "KloudMate Personal API Key",
      "password": true
    }
  ],
  "servers": {
    "kloudmate": {
      "type": "http",
      "url": "https://api.kloudmate.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:kloudmate-api-key}",
        "x-workspace-id": "YOUR_WORKSPACE_ID"
      }
    }
  }
}

Start the server from the Start action that appears above the entry, then enter your key when prompted. The tools become available to agent mode in Copilot Chat.

Claude Desktop’s custom-connector UI is built around OAuth and has no field for a bearer token, so connect through the config file using the mcp-remote bridge instead.

Open claude_desktop_config.json (Settings → Developer → Edit Config) and add:

{
  "mcpServers": {
    "kloudmate": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.kloudmate.com/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}",
        "--header",
        "x-workspace-id:YOUR_WORKSPACE_ID"
      ],
      "env": {
        "AUTH_HEADER": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The Bearer token goes in the AUTH_HEADER environment variable, and the --header argument has no spaces around the colon. That split is deliberate: it sidesteps a known bug where Claude Desktop mangles spaces inside args when it launches npx. Quit Claude Desktop fully and reopen it, because it reads the config only at startup. Then check that kloudmate appears in the tools menu.

The config file lives at:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Using a different client? Point it at https://api.kloudmate.com/mcp with an Authorization: Bearer YOUR_API_KEY header and an x-workspace-id: YOUR_WORKSPACE_ID header. Any client that speaks Streamable HTTP and lets you set request headers can connect.

Verify the connection

Once the server is connected, your client lists the KloudMate tools and your agent can call them. The quickest check is to ask a question that needs live data:

Which alerts are firing in KloudMate right now?

If the connection is healthy, the agent calls a KloudMate tool and answers from your workspace. If it reports an authentication failure, the key is likely wrong, deleted, or missing the Bearer prefix. Recheck the header and try again.

Available tools

Every tool is read-only. The server queries your telemetry; it never creates, edits, or deletes KloudMate resources. Tools accept relative time ranges like now-1h, now-15m, or now, as well as ISO-8601 timestamps, and default to the last hour when you don’t give one.

Issues and alerts

search_issues: errors and warnings aggregated from logs and traces.
search_alert_rules, search_alert_states, search_alert_states_history: list alert rules, see what’s firing now, and review how states changed over time.
search_alert_groups, get_alert_group_details: find alert groups and see a single group’s alert instances, routing rule, and any root-cause investigation attached to it.

Incidents

search_incidents, get_incident_details: find open incidents, then look up an incident by its key, such as INC-42, to read its responders, notes, alerts, and activity timeline.
get_incident_metrics: incident counts by status, plus MTTA and MTTR.

Service health (APM)

get_service_error_count, get_service_requests_count_and_avg_latency: error counts, throughput, and average latency for a service.
get_service_to_service_requests_count, get_service_to_service_failed_requests_count, get_service_to_service_request_duration: request volume, failures, and latency between services, to see which services a problem affects.

SLOs

search_slos, get_slo_details: list SLOs with their latest compliance and remaining error budget, and read a single SLO’s SLI definition, compliance history, and burn-rate alerts.
search_slo_burn_rate_alerts: burn-rate alerts across every SLO, with firing alerts listed first.

Logs, traces, and spans

search_logs, search_traces, search_spans: query telemetry with filters.
search_trace_groups: trace count, p95 duration, and error count for each service and operation, to find the busiest and slowest endpoints before you open individual traces.
get_log_details, get_span_details, get_trace_spans, get_trace_logs: pull the full record for a single log line, span, or trace.
find_cloudwatch_log_groups, search_cloudwatch_logs: find the CloudWatch log groups for an AWS resource and read their events directly from your connected AWS accounts, even for logs that aren’t sent to KloudMate.

Schema discovery

discover_dataset_fields, discover_field_values: find which fields and values exist before building a filter.
discover_metrics, discover_metric_label_values: find metric names and the values their labels take.

Aggregations and queries

run_aggregation_query, run_metric_aggregation_query: grouped counts, percentiles, and timeseries over logs and traces, or over metrics.
run_multiple_log_trace_aggregations, run_multiple_metric_aggregations: run several aggregations in one call.

Profiling

discover_profiles: list the services that send profiles and the profile types each service reports, such as CPU, allocated memory, or goroutines.
analyze_profile_hotspots, analyze_profile_trend, compare_profile_windows: find the functions using the most CPU or memory, track a profile type over time to spot a memory leak, and compare two time windows, such as before and after a deploy.

Dashboards

search_dashboards, get_dashboard_panels, run_dashboard_panel_query: find a dashboard, inspect its panels, and run a panel’s query.

Kubernetes

list_kubernetes_resources, search_kubernetes_events: inspect clusters, namespaces, deployments, and pods, and read recent cluster events.

Synthetics

search_synthetic_monitors, search_synthetic_incidents: check uptime and browser monitors and the incidents they’ve raised.

Example prompts

Once connected, ask in plain language. The agent picks the right tools and fills in the queries:

“What are the top errors in the checkout service over the last hour?”
“Show me the slowest traces for api-gateway in the past 15 minutes.”
“Which alerts are firing right now, and what changed in the half hour before they fired?”
“Pull the logs for trace 4bf92f3577b34da6 and summarize where it failed.”
“Compare request volume between the frontend and cart services this morning.”

Build custom workflows

Your agent can chain these tools and combine them with whatever else it can reach, such as your codebase, a runbook, or your deployment history. You can turn an investigation that takes several screens in the KloudMate UI into a repeatable workflow.

A triage workflow, for example, might pull the currently firing alerts, scope the affected services with the service-to-service tools, gather the relevant traces and logs, and hand you a single summary with a probable cause. Save it as a reusable command or prompt in your tool of choice, and the next on-call run is one sentence instead of twenty clicks.

Security and scope

A few things worth keeping in mind:

Read-only. The server can’t change anything in your workspace. Connecting it can’t cause an outage or alter a dashboard.
Scoped to you. The key carries your own account’s permissions, and the x-workspace-id header picks which workspace each request reads. It can’t reach a workspace you can’t.
Keep the key secret. Prefer the environment-variable or prompted-secret options above over pasting the key into a file. Add config files that contain a key to .gitignore.
Delete when needed. If a key is exposed or no longer used, delete it from the Personal API Keys screen in your account menu. Any client using it stops working immediately.

API Keys Create the personal key the MCP server authenticates with, and manage ingest keys.

MCP Integrations Connect external MCP servers and tools into the KloudMate Assistant.

Investigations Run AI-assisted root cause analysis inside KloudMate.

KloudMate Assistant The in-app AI assistant for monitoring, dashboards, and RCA.