Compatible with every major AI agent and IDE
What is the Prometheus MCP Server?
Connect your Prometheus instance to any AI agent and transform your observability data into actionable insights through natural conversation.
What you can do
- Instant & Range Queries — Evaluate complex PromQL expressions for real-time status or historical trends over specific time windows.
- Metric Discovery — Find time series matching specific label selectors and explore available labels and their values across your environment.
- Metadata Inspection — Retrieve detailed metadata about metrics scraped from targets to understand units, types, and help text.
- Admin Operations — Create data snapshots, delete specific series, and clean tombstones (requires admin API enabled).
- System Status — Inspect your Prometheus configuration, flags, and runtime information to ensure your monitoring stack is healthy.
How it works
- Subscribe to this server
- Enter your Prometheus Server URL (and optional Auth Token)
- Start querying your metrics from Claude, Cursor, or any MCP-compatible client
No more manual dashboard building just to answer a quick question about system health. Your AI acts as a dedicated SRE or DevOps engineer.
Who is this for?
- SRE & DevOps Engineers — instantly troubleshoot incidents by querying metrics and checking configurations without leaving the terminal or chat.
- Backend Developers — verify service performance and resource consumption directly from the code editor.
- Platform Teams — automate infrastructure health reports and audit monitoring configurations via natural language.
Built-in capabilities (14)
enable-admin-api to be enabled. Remove deleted data from disk
enable-admin-api to be enabled on the Prometheus server. Create a snapshot of all current data
enable-admin-api to be enabled. Delete data for a selection of series in a time range
Find time series matching label selectors
Get all values for a specific label
Get a list of all label names
Get metadata about metrics scraped from targets
Get Prometheus build information
Get the currently loaded Prometheus configuration (YAML)
Get configured Prometheus flag values
Get Prometheus runtime information
Get TSDB cardinality statistics
Evaluate a PromQL expression at a single point in time
Evaluate a PromQL expression over a range of time
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Prometheus through native MCP adapters. Connect 14 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Prometheus MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Prometheus queries for multi-turn workflows
Prometheus in LangChain
Prometheus and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Prometheus to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Prometheus in LangChain
The Prometheus MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Prometheus for LangChain
Every tool call from LangChain to the Prometheus MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I run a PromQL query to get the current value of a metric?
Yes. Use the query tool to evaluate any PromQL expression at a single point in time. This is perfect for checking current CPU usage, memory levels, or error rates.
How do I see how a metric has changed over the last hour?
Use the query_range tool. You can specify the start and end timestamps along with a step duration to retrieve historical data points for graphing or trend analysis.
Can I perform administrative tasks like creating backups?
Yes, if your Prometheus server has the Admin API enabled (--web.enable-admin-api), you can use the create_snapshot tool to create a snapshot of all current data on disk.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters
Explore More MCP Servers
View all →
Churnkey
8 toolsManage customer retention and cancellation flows via Churnkey — track sessions, analyze exit surveys, and automate recovery contacts directly from any AI agent.

Cannlytics Strain API
5 toolsAccess cannabis strain data, effects, flavors, and similar strains via Cannlytics.

Volvo Cars Connected
10 toolsMonitor and manage your connected Volvo vehicle — check fuel levels, battery status, door locks, and trip statistics directly via AI.

Luma AI (Generative Video & Creative)
10 toolsGenerate cinematic AI videos and images via Luma — use Dream Machine for text-to-video, image-to-video, and professional camera control.
