4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
Prometheus MCP Server

Bring Prometheus
to VS Code Copilot

Learn how to connect Prometheus to VS Code Copilot and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Clean TombstonesCreate SnapshotDelete SeriesFind SeriesGet Label ValuesGet LabelsGet MetadataGet Status BuildinfoGet Status ConfigGet Status FlagsGet Status RuntimeinfoGet Status TsdbQueryQuery Range

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Prometheus

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

  1. Subscribe to this server
  2. Enter your Prometheus Server URL (and optional Auth Token)
  3. 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)

clean_tombstones

enable-admin-api to be enabled. Remove deleted data from disk

create_snapshot

enable-admin-api to be enabled on the Prometheus server. Create a snapshot of all current data

delete_series

enable-admin-api to be enabled. Delete data for a selection of series in a time range

find_series

Find time series matching label selectors

get_label_values

Get all values for a specific label

get_labels

Get a list of all label names

get_metadata

Get metadata about metrics scraped from targets

get_status_buildinfo

Get Prometheus build information

get_status_config

Get the currently loaded Prometheus configuration (YAML)

get_status_flags

Get configured Prometheus flag values

get_status_runtimeinfo

Get Prometheus runtime information

get_status_tsdb

Get TSDB cardinality statistics

query

Evaluate a PromQL expression at a single point in time

query_range

Evaluate a PromQL expression over a range of time

Why VS Code Copilot?

GitHub Copilot Agent mode brings Prometheus data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Prometheus in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Prometheus and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Prometheus to VS Code Copilot 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Prometheus in VS Code Copilot

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 VS Code Copilot 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.

Prometheus
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures Prometheus for VS Code Copilot

Every tool call from VS Code Copilot to the Prometheus MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →