Can I check if a specific website is down using the agent?

Yes! Use the `list_monitors` tool to see the status of all your monitored URLs. You can also use `get_monitor` with a specific ID to see its current status and last checked timestamp.

How do I see who is currently on-call?

Simply ask the agent to `list_on_calls`. It will retrieve the current schedules and rotations, showing you who is responsible for incident response right now.

Does the integration allow me to create a new heartbeat monitor?

Currently, the toolset focuses on managing monitors and retrieving incident/on-call data. You can list and inspect heartbeats, but for creating new monitors with complex notification rules, we recommend using the Better Stack dashboard.

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": {
      "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 (formerly Better Uptime) account to any AI agent and orchestrate your infrastructure monitoring and incident management through natural 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

Uptime Monitoring — List, create, and manage all your HTTP, Ping, and Keyword monitors to ensure service availability.
Incident Response — Retrieve real-time updates on active incidents and historical reports for post-mortems.
On-Call Coordination — Access on-call schedules and rotations to see who is responsible for system health.
Heartbeat Management — Monitor cron jobs and recurring tasks through heartbeat monitors.
Status Page Oversight — List and verify your public status pages directly from your workspace.

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:

create_monitor

Create a new uptime monitor

delete_monitor

Delete a monitor

get_incident

Get details of a specific incident

get_monitor

Get specific monitor details

list_heartbeats

List all heartbeat monitors

list_incidents

List recent uptime incidents

list_monitors

List all uptime monitors

list_on_calls

List on-call schedules and rotations

list_status_pages

List public status pages

update_monitor

Update an existing monitor

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 all monitors that are currently down."

"Show me the on-call schedule for this week."

"Check status of heartbeat 'daily-backup'."

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.