Skip to content

Datadog MCP connector

The Datadog connector brings monitors, incidents, logs, traces, metrics and dashboards from your Datadog region into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so your team can ask about production in plain language.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card

Regions: US1, US3, US5, EU, UK1, AP1 and AP2. Elaichi supports all of them; you pick your region when you connect.

ChatGPT Elaichi connected

Which monitors are alerting right now and on which hosts?

Working in Datadog with Elaichi

  • Search Datadog events
  • Get Datadog incident
  • Get Datadog metric
Ask anything…
Governance / Audit log Last 24 hours
Datadog Get Datadog metric Emily Carter · ChatGPT · 9:41 AM Done
Datadog Get Datadog incident Emily Carter · ChatGPT · 9:41 AM Done
Datadog Search Datadog events Emily Carter · ChatGPT · 9:41 AM Done
Datadog Get Datadog metric context Megan Brooks · Claude · 9:38 AM Done
Datadog Search Datadog monitors Ryan Hayes · Cursor · 9:35 AM Done

How to connect Datadog to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Datadog MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Datadog MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Datadog MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Datadog MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Datadog MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Datadog to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Datadog through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Datadog is logged.

  • SRE

    Pull the picture together during an incident

    Ask what fired, which hosts are affected and what the error logs say while the incident in Datadog is still open. Get the answer in one place instead of six tabs.

  • Engineering

    Trace a slow request to its cause

    Find the spans behind a slow endpoint, compare them with the metric for that service and see where the time goes.

  • Support

    Check whether a customer's problem is real

    When a customer reports errors, look up the RUM events and logs for their session in Datadog before replying, so the answer is grounded in what actually happened.

  • Platform

    Review monitors before they go live

    Validate a new monitor against Datadog, compare it with the monitor templates your team already uses and check which monitor group it belongs in.

  • Engineering leadership

    Write the postmortem from the real timeline

    Search events and incidents for the window in question, then create a notebook in Datadog with the timeline and the metrics that mattered, ready for the review.

  • Security

    Look for unusual activity in logs

    Analyze logs across hosts in Datadog for failed logins, unexpected geographies or spikes from a single source, and search the dashboards your team already built for the same signal.

Try asking

  • “Which monitors are alerting right now and on which hosts?”
  • “Summarize the error logs for the checkout service in the last hour.”
  • “Draft a notebook with the timeline of incident 4821.”

See all 352 Datadog tools →

What connecting Datadog gets you

6 screens from Elaichi, each doing one job for your Datadog account.

Elaichi Agent

Ask Elaichi to work across your apps.

Which monitors are alerting right now and on which hosts?

Summarize the error logs for the checkout service in the last hour.

Draft a notebook with the timeline of incident 4821.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about production in plain language.

Which monitors are alerting, what the logs say, answered from live Datadog records.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One governed endpoint for Claude, ChatGPT, Cursor and Microsoft Copilot.

Datadog from any MCP client over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
Search Datadog events Search Searches events like monitor alerts, deployment notifications, infrastructure changes, security findings, and service status changes.
Get Datadog incident Get Retrieves detailed information about an incident.
Get Datadog metric Get Queries and analyzes historical or real-time metric data, supporting custom queries and aggregations.
Get Datadog metric context Get Retrieves detailed information about a metric including metadata, available tags, and tag values for filtering and grouping.
Search Datadog monitors Search Retrieves information about Datadog monitors, including their statuses, thresholds, and alert conditions.

Tool catalog

352 Datadog tools, no code to write.

Monitors, incidents, logs, traces, metrics, dashboards and notebooks, all cataloged and ready to call.

ElaichiToolboxes
Name Source template Tools Created

SRE toolbox

Datadog · incidents and monitors

Datadog starter 18 Mar 4, 2026

Engineering toolbox

Datadog · traces, spans and metrics

— 9 Mar 2, 2026

Support toolbox

Datadog · logs and RUM events

— 24 Feb 27, 2026

Platform toolbox

Datadog · hosts and monitor templates

Datadog starter 6 Feb 19, 2026

Security toolbox

Datadog · log analysis and events

— 31 Jan 30, 2026

Product toolbox

Datadog · RUM events and dashboards

— 12 Jan 22, 2026

Toolboxes

Every team gets its own toolbox.

Scope SRE to incidents and Support to logs, each toolbox built for one team's work.

ElaichiConnections
Connection Scope Status Access
DA

Datadog (Production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
DA

Datadog (Staging)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
DA

Datadog (Platform)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
DA

Datadog (Support)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
DA

Datadog (Security)

Connected by Ryan Hayes

Personal • Active Not shared
DA

Datadog (Payments)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates work through a connection, never a credential.

See who connected each Datadog account and which teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Datadog Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Datadog Monitors Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Datadog Monitors List Toolbox

Audit log

Every call answers who did what.

When, who, what happened, type and resource, for every search of Datadog logs.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Datadog digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch monitors

    Datadog

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Datadog

    Queued

Workflows

A schedule starts the work, a person approves.

Incidents are fetched, grouped, drafted into a digest, then posted to Datadog after approval.

Datadog health

Refreshed 4 minutes ago · every 15 minutes · from the monitors collection

Live

Monitors

1,284 ↓ 12%

Incidents

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Monitors created

Last 14 days

By team

Share of activity

Production 34%

Staging 27%

Platform 21%

Support 18%

Collections and dashboards

Incident health, computed, with no model involved.

Four metrics, 14 days of incidents created and a team breakdown, refreshed on a schedule.

Why connect Datadog's MCP server through Elaichi

Datadog builds and runs this MCP server. Elaichi sits in front of it, so Datadog's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Datadog's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Datadog's tools at the same Elaichi address as every other connected app. Nobody adds Datadog's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Datadog sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Datadog's server. By default, a tool Datadog does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Datadog

    Datadog builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Datadog team.

    help.datadoghq.com/hc/en-us

Why run a vendor's MCP server through Elaichi →

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Datadog

All three can connect Datadog to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Datadog, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Datadog tools Allow or restrict single Datadog tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Datadog call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Datadog tools for your AI agents

352 tools are ready to call through Elaichi's MCP endpoint the moment you connect Datadog, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Datadog builds and runs these tools.

Showing 317 of 352 Datadog tools here. Connect Datadog and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

How do I connect Datadog to Claude?

Connect Datadog in Elaichi first, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Datadog's own step is a normal OAuth sign-in: you log in to your Datadog account and approve access. There is no OAuth application to register and no client ID or secret to generate.

Does Datadog work with ChatGPT and Cursor as well as Claude?

Yes. Once Datadog is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Datadog once and every client picks it up.

What can an AI agent actually do with my Datadog data?

It can search monitors, incidents, events, logs, traces, spans, hosts, metrics, RUM events and dashboards in Datadog, and it can create or edit notebooks and validate a monitor definition before you save it. Ask it which monitors are alerting right now, what the error logs for a service say, or to draft a notebook with an incident's timeline. Short, concrete asks like these work better than long sentences.

Does connecting Datadog give the AI access to my whole organization?

No. Every call to Datadog runs as the person who signed in, so the AI sees exactly the dashboards, logs and monitors that person can already see in Datadog, and nothing more. Elaichi can narrow that access further with restrictions, but it can never widen it beyond what Datadog itself grants.

Can my team share one Datadog connection?

Yes. One person connects Datadog in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every search of Datadog.

Can I stop an agent from changing things in Datadog?

Yes. Restrictions in Elaichi apply per action, so you can allow searching monitors, logs and incidents in Datadog while restricting the creation or editing of notebooks. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

What happens to a Datadog connection when someone leaves?

Offboarding that person in Elaichi ends their access to Datadog at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. If they had shared a Datadog connection with a team, it keeps working for everyone else. Disconnecting Datadog once in Elaichi removes it from every client.

Does the Datadog MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Datadog is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Datadog?

Yes. Both let Claude, ChatGPT or Cursor use Datadog. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Datadog call.

How is Elaichi different from Composio for Datadog?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Datadog: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Datadog in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot