Datadog MCP Server for VS Code CopilotGive VS Code Copilot instant access to 16 tools to Check Datadog Status, Create Event, Get Dashboard, and more
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.
Ask AI about this App Connector for VS Code Copilot
The Datadog app connector for VS Code Copilot is a standout in the Loved By Devs category — giving your AI agent 16 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Datadog and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"datadog-extended": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 observability stack 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 16 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Monitor Management — List, search, inspect, and mute monitors to control alert noise during maintenance windows
- Dashboard Inspection — Browse dashboards and retrieve full layouts, widgets, and template variables
- Metric Queries — Run time-series queries using Datadog syntax (e.g.,
avg:system.cpu.user{*}) with custom time ranges - Log Search — Search log events using Datadog query syntax across all indexed log sources
- Event Tracking — Browse platform events and create custom events with tags and priority levels
- Incident Management — List active incidents with severity, status, responders, and timeline details
- SLO Monitoring — Review Service Level Objectives with targets, error budgets, and compliance status
- Host Inventory — Access all reporting hosts with metadata, tags, and agent versions
The Datadog MCP Server exposes 16 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.
All 16 Datadog tools available for VS Code Copilot
When VS Code Copilot connects to Datadog through Vinkius, your AI agent gets direct access to every tool listed below — spanning full-stack-monitoring, infrastructure-metrics, log-analysis, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Verify connectivity
Create an event
Get dashboard details
Get incident details
Get monitor details
List dashboards
List events
List hosts
List incidents
List metrics
List monitors
List SLOs
Mute a monitor
Query metric data
Search logs
Search monitors
Connect Datadog to VS Code Copilot via MCP
Follow these steps to wire Datadog into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Datadog
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.
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
Datadog + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Datadog 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
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.
"Show all monitors that are currently alerting and mute the noisiest one."
"Search for error logs in production from the last hour."
"List all SLOs and tell me which ones are at risk of breaching their error budget."
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.
MCP tools not available
Datadog + VS Code Copilot FAQ
Common questions about integrating Datadog MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.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.