Bring Service Health
to VS Code Copilot
Learn how to connect Gatus (Health Dashboard) to VS Code Copilot and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Gatus (Health Dashboard) MCP Server?
Connect your Gatus health dashboard to any AI agent to monitor your services and infrastructure through natural conversation.
What you can do
- Global Visibility — List all monitored endpoints and their current health status across your entire infrastructure.
- Deep Health Inspection — Drill down into specific services to see recent results and status history using slugified keys.
- Performance Statistics — Retrieve performance metrics for individual endpoints to identify latency or reliability issues.
- Metrics Export — Access raw Prometheus-compatible metrics for deep technical analysis and custom reporting.
How it works
- Subscribe to this server
- Enter your Gatus instance URL
- Start monitoring your system health from Claude, Cursor, or any MCP-compatible client.
No more manual dashboard checking. Your AI acts as a 24/7 SRE assistant, providing instant insights into your service availability.
Who is this for?
- DevOps Engineers — quickly audit service health and retrieve raw metrics without leaving the terminal or IDE.
- SRE Teams — investigate performance regressions and endpoint history through natural language queries.
- Product Owners — get high-level status reports on system availability during incidents.
Built-in capabilities (4)
Get health status and recent results for a specific endpoint
Get performance statistics for a specific endpoint
Get Prometheus-compatible metrics from Gatus
Get all monitored endpoints and their current status
Why VS Code Copilot?
GitHub Copilot Agent mode brings Gatus (Health Dashboard) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 4 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
Gatus (Health Dashboard) in VS Code Copilot
Gatus (Health Dashboard) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Gatus (Health Dashboard) 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.
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 Gatus (Health Dashboard) in VS Code Copilot
The Gatus (Health Dashboard) 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 4 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.
* 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
Gatus (Health Dashboard) for VS Code Copilot
Every tool call from VS Code Copilot to the Gatus (Health Dashboard) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the status of all my services at once?
Yes! Use the list_endpoints tool to retrieve a complete list of all configured endpoints and their current health status across your Gatus instance.
How do I check the performance history of a specific service?
You can use get_endpoint_stats with the endpoint's slugified key to see detailed performance statistics, or get_endpoint_health for recent health check results.
Does this server provide raw metrics for analysis?
Yes, the get_metrics tool retrieves raw Prometheus-compatible metrics exported by Gatus, allowing your AI to perform deep technical analysis.
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.
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.
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.
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.
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 →
AskHandle Alternative
18 toolsManage AI chat rooms, capture leads, and automate messaging workflows directly through AskHandle.
FRED Full Access — U.S. Economic Intelligence
19 toolsThe ultimate U.S. economic data Mega-Server: 19 tools covering time series, releases, categories, regional GeoFRED data, tags, and 107 data sources — 816,000+ series from the Federal Reserve in one integration.
BOSSDesk
10 toolsManage your IT services via BOSSDesk — track tickets, assets, and users directly from any AI agent.
Resend
10 toolsAutomate transactional and broadcast email delivery via Resend — send messages, manage domains, audiences, and contacts directly from any AI agent.