Prometheus MCP Server

Created By
pab1it0a year ago
A Model Context Protocol (MCP) server that enables AI assistants to query and analyze Prometheus metrics through standardized interfaces.
Overview

What is Prometheus MCP Server?

Prometheus MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to query and analyze Prometheus metrics through standardized interfaces.

How to use Prometheus MCP Server?

To use the Prometheus MCP Server, ensure your Prometheus server is accessible, configure the necessary environment variables, and run the server either directly or using Docker.

Key features of Prometheus MCP Server?

  • Execute PromQL queries against Prometheus.
  • Discover and explore metrics, including listing available metrics and viewing query results.
  • Support for authentication via basic auth or bearer token.
  • Docker containerization for easy deployment.
  • Interactive tools for AI assistants with configurable options.

Use cases of Prometheus MCP Server?

  1. Enabling AI assistants to perform real-time analysis of Prometheus metrics.
  2. Facilitating automated monitoring and alerting based on Prometheus data.
  3. Providing a standardized interface for querying metrics across different applications.

FAQ from Prometheus MCP Server?

  • What is the purpose of the Prometheus MCP Server?

It enables AI assistants to interact with Prometheus metrics using a standardized protocol.

  • Is Docker required to run the server?

No, Docker is optional; you can run the server directly if preferred.

  • What authentication methods are supported?

The server supports basic authentication and bearer token authentication.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pab1it0
Star
89
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago