Can my AI automatically acknowledge an incident so my phone stops ringing?

Yes! Running the `acknowledge_incident` capability pushes a verified API command halting escalation cycles (like SMS and phone calls) natively while you debug.

Is it possible to see the exact HTTP response body or headers that caused a monitor to fail?

Yes, pulling details via `get_incident` exposes the raw nested trace containing the root cause payloads and server errors Better Stack historically received when the check failed.

Can the agent create new monitors automatically?

No. The integration focuses safely on observation, alerting resolution, and tracking currently. Creation endpoints represent mutation vectors decoupled to ensure you preserve billing and account structure intentionally.

Better Stack MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Better Stack
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Better Stack and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "better-stack-1": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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

About Better Stack MCP Server

Connect your Better Stack (Better Uptime) account to any AI agent and empower it to act as your Level 1 Site Reliability Engineer (SRE). Let your AI diagnose incidents, manage escalations, and audit monitoring configs securely via conversation.

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

What you can do

Incident Response — Rapidly list firing incidents, inspect technical downtime payloads, acknowledge alerts, and force resolve states inline
Uptime Monitors — Fetch exact definitions of active HTTP endpoint pings, DNS probes, and latency constraints across your fleet
Cron Heartbeats — Investigate passive tracking endpoints validating background workers and server limits
On-Call Management — Expose active shifts and team schedules to determine explicitly who is getting paged in real-time
Status Pages — Read configured public dashboards tracking your global infrastructure

The Better Stack MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Better Stack to VS Code Copilot via MCP

Follow these steps to integrate the Better Stack MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Better Stack

Ask Copilot: "Using Better Stack, help me...". 10 tools available

Why Use VS Code Copilot with the Better Stack MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Better Stack through the Model Context Protocol.

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

Better Stack + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Better Stack MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Better Stack MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Better Stack to VS Code Copilot via MCP:

acknowledge_incident

Acknowledge an ongoing explicit incident halting paging

get_heartbeat

Get explicit details of a passive heartbeat node

get_incident

Retrieve the native timeline payload of an explicit incident

get_monitor

Get full details of a specific Better Stack monitor

list_heartbeats

List all configured cron heartbeats securely

list_incidents

List all explicit incidents on Better Stack

list_monitors

List all monitors on Better Stack (Better Uptime)

list_on_call

List exact On-Call routing calendars

list_status_pages

List all explicit Status Pages

resolve_incident

Force resolve a specific incident

Example Prompts for Better Stack in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Better Stack immediately.

"List any active unresolved incidents going on right now."

"Who is currently on-call for the main engineering shift?"

"Check the detailed root cause of passed Incident #8012."

Troubleshooting Better Stack MCP Server with VS Code Copilot

Common issues when connecting Better Stack to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

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

Better Stack + VS Code Copilot FAQ

Common questions about integrating Better Stack MCP Server with VS Code Copilot.

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.