Observability Agent MCP

A portable, read-only Model Context Protocol server for turning observability data into bounded evidence that AI agents can inspect safely.

Status

Runnable provider-backed MCP. The TypeScript server exposes seven bounded, read-only tools over stdio and authenticated Streamable HTTP. It includes VictoriaMetrics/Prometheus-compatible metrics and alert adapters, allowlisted Grafana PNG rendering, deterministic local fixtures, npm packaging, and a non-root OCI runtime. Private deployment configuration remains outside this public repository.

Related MCP server: Observe MCP Server

Product Boundary

This project provides deterministic tools for observability evidence. It does not run an LLM, receive chat messages, execute shell commands, deploy workloads, or remediate production systems.

AI client
  | stdio (implemented)
  v
Observability Agent MCP
  - strict tool schemas
  - query and response limits
  - label and value redaction
  - normalized evidence bundles
  |
  +--> deterministic fake provider
  +--> allowlisted Grafana render API
  +--> named-query Prometheus-compatible API
       +--> VictoriaMetrics alert API
       - Prometheus
       - VictoriaMetrics

The model and agent loop remain in the client. This server only returns structured evidence.

First Tool Set

Version 1 is read-only. It will not create dashboards, modify alert rules, silence alerts, restart services, run scripts, or trigger deployments.

Portability

The server can be consumed through:

• stdio for local desktop and CLI agents;

• an authenticated Streamable HTTP endpoint on a private network;

• a non-root OCI image;

• the package CLI produced by npm pack.

The implemented HTTP mode uses a file-injected Bearer credential and a strict Host allowlist for a private, single-operator deployment. It is not a public or multi-tenant OAuth deployment. No package or image has been published yet.

Remote HTTP deployment requires authentication. Publishing this repository does not imply that an MCP endpoint should be exposed without OAuth, network policy, rate limits, and audience-bound scopes.

Run Locally

Node.js 22 and npm are required.

npm ci
npm run build
node dist/cli.js

The process speaks MCP over stdio, so launch it from an MCP client rather than typing into the terminal. A client command definition is:

{
  "command": "node",
  "args": ["/absolute/path/to/observability-agent-mcp/dist/cli.js"]
}

Inspect tool discovery and run every local gate with:

npm run inspector:list
npm run validate

Build and run the non-root OCI image over stdio with:

npm run container:build
docker run --rm -i observability-agent-mcp:local

Production HTTP mode requires a strict YAML provider policy and two 0600 runtime credential files. See Client Compatibility and Security Model before deploying it.

Relationship To Grafana MCP

The official Grafana MCP server is the preferred reference and fast path for broad Grafana capabilities. This project will not duplicate its dashboard and administration surface.

The unique scope here is:

• compact incident-context evidence;

• conservative read-only defaults;

• direct Prometheus-compatible operation when Grafana is absent;

• provider-neutral schemas;

• predictable limits and redaction for agent use.

Grafana visuals are first-class evidence. Rendering tools return an MCP ImageContent PNG plus structured metadata for the source, observation window, dimensions, byte size, freshness, truncation, and warnings. Visuals are opt-in; normal metric queries do not spend rendering resources or image context.

There is no automatic delegation between the two servers. Use Grafana MCP when an agent needs Grafana-native dashboards, incidents, administration, or its existing query tools. Use this project's namespace when the client needs the same bounded evidence contract across Grafana and direct Prometheus-compatible backends. active_alerts and incident_context are normalized here rather than forwarded to Grafana MCP; query_metrics selects one configured adapter and never calls another MCP server. Deployments may offer both namespaces, but each request has one explicit owner.

Read Next

• Architecture

• Security Model

• Tool Surface

• Client Compatibility

• Test Strategy

• Roadmap

• Implementation Status

• Grafana Visual Context ADR

• Contributing

License

Apache License 2.0. See LICENSE.