Prometheus MCP Server

Created By
moohooramaa year ago
Overview

what is Prometheus MCP Server?

Prometheus MCP Server is a tool that allows access to Prometheus data through a Model Context Protocol server.

how to use Prometheus MCP Server?

To use the Prometheus MCP Server, you can either install it using pipx or run it directly without installation. For installation, use the command: pipx install git+https://github.com/moohoorama/prometheus-mcp-server-py.git. To run without installation, use: pipx run --spec git+https://github.com/moohoorama/prometheus-mcp-server-py.git prometheus-mcp --url http://your-prometheus-server:9090.

key features of Prometheus MCP Server?

  • Access Prometheus data through a Model Context Protocol server.
  • Supports basic authentication and token-based authentication.
  • Multi-tenant support with organization ID.

use cases of Prometheus MCP Server?

  1. Accessing Prometheus metrics for monitoring applications.
  2. Integrating Prometheus data with other services using the MCP protocol.
  3. Testing Prometheus setups without permanent installation.

FAQ from Prometheus MCP Server?

  • Can I run the server without installing it?

Yes! You can run it directly using pipx without installation.

  • What authentication methods are supported?

The server supports basic authentication (username and password) and token-based authentication.

  • Is there support for multi-tenant setups?

Yes! You can specify an organization ID for multi-tenant configurations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
moohoorama
Star
0
Language
Python
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