MCP Prometheus Server

Created By
drewstreiba year ago
A sophisticated MCP server for Prometheus queries demonstrating advanced Haskell practices
Overview

what is MCP Prometheus Server?

MCP Prometheus Server is a sophisticated server implementation for the Model Context Protocol (MCP) that allows access to Prometheus metrics and queries, showcasing advanced Haskell practices.

how to use MCP Prometheus Server?

To use the MCP Prometheus Server, you can either clone the repository and use the pre-built binary, build from source, or run it using Docker. Configuration is required for integration with Claude Desktop.

key features of MCP Prometheus Server?

  • 🚀 Claude Desktop Integration - Seamless support for MCP protocol.
  • 📊 Complete Prometheus API - Query, discover, and explore metrics.
  • 🔍 5 Powerful Tools - Instant queries, metric discovery, and more.
  • 🛡️ Production Ready - Comprehensive error handling and logging.
  • 🧵 Thread Safe - Strict evaluation prevents lazy I/O hangs.
  • 🔧 Haskell Best Practices - Proper exception handling and robust operation.

use cases of MCP Prometheus Server?

  1. Integrating Prometheus metrics into applications.
  2. Monitoring system performance through Prometheus queries.
  3. Developing Haskell applications with robust error handling and logging.

FAQ from MCP Prometheus Server?

  • Can I run MCP Prometheus Server in Docker?

Yes! You can run it using Docker for development purposes.

  • What are the prerequisites for building from source?

You need GHC 9.12+ and Cabal 3.0+.

  • How do I configure the server for Claude Desktop?

You need to add the server command to your Claude Desktop configuration file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
drewstreib
Star
0
Language
Haskell
License
BSD-3-Clause 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)

3 hours ago
Myrsu
@VidhiJav

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago