Bring Full Stack Monitoring
to Claude Desktop
Learn how to connect Datadog to Claude Desktop and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Datadog MCP Server?
Connect your Datadog account to any AI agent and take full control of your observability stack through natural conversation.
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
How it works
1. Subscribe to this server
2. Enter your Datadog API Key and your site URL (e.g., https://api.datadoghq.com for US or https://api.datadoghq.eu for EU)
3. Start monitoring your infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- SRE / DevOps Engineers — query monitors, mute noisy alerts, and inspect incidents without opening the Datadog dashboard
- Platform Teams — run metric queries and validate SLO compliance through conversational AI
- On-Call Engineers — triage incidents, search error logs, and check host health during outages via natural language
Built-in capabilities (16)
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
Why Claude Desktop?
Claude Desktop is the definitive way to connect Datadog to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 16 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Datadog in Claude Desktop
Datadog and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Datadog to Claude Desktop 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 | 3,400+ 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 Datadog in Claude Desktop
The Datadog 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 16 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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
Datadog for Claude Desktop
Every tool call from Claude Desktop to the Datadog MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I silence noisy monitors during scheduled maintenance?
Yes. The mute_monitor action silences a specific monitor by its ID, suppressing all alert notifications. This is ideal during deployment windows or planned maintenance. Use search_monitors to find the monitor by name or tag first, then mute it by ID.
Does Datadog require two credentials to connect?
Yes. You need your API Key (found in Organization Settings > API Keys) and your Base URL, which depends on your Datadog site region: https://api.datadoghq.com for US1, https://api.datadoghq.eu for EU, or https://api.us3.datadoghq.com for US3. The API Key is sent via the DD-API-KEY header.
Can I run time-series metric queries with custom time ranges?
Yes. The query_metrics tool accepts a Datadog metric query string (e.g., avg:system.cpu.user{host:web-01}), a start epoch timestamp, and an end epoch timestamp. It returns the time-series data points for that metric across the specified window.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.