2,500+ MCP servers ready to use
Vinkius

Datadog MCP Server for VS Code Copilot 11 tools — connect in under 2 minutes

Built by Vinkius GDPR 11 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.

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 Datadog and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "datadog": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Datadog
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 Datadog MCP Server

Connect your Datadog account to any AI agent and take full control of your infrastructure monitoring and log management through natural conversation.

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

What you can do

  • Metric Auditing — Execute static queries targeting numeric telemetry datastores to resolve specific DDQL metrics objects generated dynamically
  • Log Investigation — Perform structural extraction matching target string traces inside Datadog logs to evaluate status boundaries across your apps
  • Monitor Management — Discover explicit system rule endpoints bounding configured triggers against alert metrics to verify health states
  • Telemetry Extraction — Fetch timestamp arrays natively from numeric logged endpoints to analyze performance trends over specific time intervals
  • Log Filtering — Apply ISO boundary mappings to compare logging payloads and identify exactly when errors or bottlenecks occurred

The Datadog MCP Server exposes 11 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 Datadog to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Datadog

Ask Copilot: "Using Datadog, help me..."11 tools available

Why Use VS Code Copilot with the Datadog MCP Server

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

01

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

02

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

03

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

04

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

Datadog + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Datadog MCP Tools for VS Code Copilot (11)

These 11 tools become available when you connect Datadog to VS Code Copilot via MCP:

01

get_dashboard

Resolves all widget configurations, template variables, and layout structures for visualization rendering. Get dashboard details

02

get_monitor

Resolves notification settings, threshold values, and historical status changes for the given monitor ID. Get monitor details

03

list_dashboards

Returns a list of dashboard identifiers, titles, layout types (timeboard/screenboard), and direct access URLs. List all dashboards

04

list_downtimes

Returns scope tags, recurring schedules, and current status to identify planned maintenance periods. List scheduled downtimes

05

list_events

Returns a collection of events including titles, priority levels, and source identifiers (e.g., monitor alerts, deployment events). List events

06

list_hosts

Returns host metadata including agent version, active tags, and associated cloud provider attributes. List infrastructure hosts

07

list_monitors

Filters results by operational state (alert, warn, no data, ok) and returns monitor metadata including type, query, and current status. List monitors by state

08

list_slos

Returns SLO definitions including target percentages, time windows, and current compliance status for monitor-based or metric-based objectives. List Service Level Objectives

09

mute_monitor

Interacts with the alerting boundary to set temporary silence periods, optionally with an automatic expiration timestamp. Mute a monitor

10

query_metrics

Resolves time-series data within the specified UNIX timestamp range. Returns metric points, scope tags, and unit metadata for infrastructure and application monitoring. Query time-series metrics

11

search_logs

Interacts with the log storage boundary to retrieve entries matching the query syntax, including timestamps, status levels, and structured attributes. Search application logs

Example Prompts for Datadog in VS Code Copilot

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

01

"Show me the CPU usage for 'web-server' over the last 30 minutes"

02

"Find logs with '500 Internal Server Error' from the last hour"

03

"Are there any active monitors in 'Alert' state?"

Troubleshooting Datadog MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Datadog + VS Code Copilot FAQ

Common questions about integrating Datadog MCP Server with VS Code Copilot.

01

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.
02

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.
03

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.
04

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.

Connect Datadog to VS Code Copilot

Get your token, paste the configuration, and start using 11 tools in under 2 minutes. No API key management needed.