Skip to content

Datadog (US3) MCP connector

The Datadog (US3) connector brings logs, metrics, traces, monitors, incidents and notebooks from your Datadog US3 account to Claude, ChatGPT, Cursor and the Elaichi agent, where each person asks questions as themselves.

  • How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Datadog (US3) to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Datadog (US3) once

  1. Open Connections, choose Add connection, and pick Datadog (US3).

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Datadog (US3). Datadog (US3)'s own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

datadog (us3)
Datadog (US3)
Datadog (US1)
Datadog (AP1)
Datadog (AP2)
Datadog (EU)
Datadog (UK1)
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Datadog (US3) 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 (US3) 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 today. The plugin directory lives at chatgpt.com/plugins.

Datadog (US3) 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.

Connect Datadog (US3) 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.

Use cases

What teams do with Datadog (US3) through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • On-call

    Get the picture before joining the bridge

    Ask which monitors are alerting, pull the open incident, and read the related logs and traces in one place before you join the call.

  • Platform

    Find the host that is running hot

    Search hosts and metrics for the service in question and get a plain answer about which machines are under pressure and since when.

  • Backend

    Trace a slow request end to end

    Pull the trace for a slow request, aggregate the spans, and see which downstream call is eating the time.

  • Frontend

    See what users hit in the browser

    Search and aggregate RUM events to find which pages errored for real users this morning and how many sessions were affected.

  • Support

    Check the logs behind a customer ticket

    Search logs for the customer's account around the time they reported the problem, and attach what you found to the ticket.

  • Engineering

    Write up the incident in a notebook

    Create a notebook from the incident, add the timeline and the key metrics, and edit it as the review takes shape.

Try asking

  • “Which monitors are alerting in production right now?”
  • “Summarize the open incidents from the last 24 hours.”
  • “Show error logs for the checkout service since midnight.”

See all 352 Datadog (US3) tools below

Compare

Elaichi vs Zapier MCP vs Composio for Datadog (US3)

All three can connect Datadog (US3) 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 (US3), 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 (US3) tools Allow or restrict single Datadog (US3) 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 (US3) 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 $15 per user per month. 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.

AI tools

Datadog (US3) tools for your AI agents

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

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

See it in Elaichi

What connecting Datadog (US3) gets you

6 screens from the product, each doing one job for your Datadog (US3) account.

The agent

Ask about last night's incident in plain language.

Logs, metrics, monitors and incidents from Datadog (US3), answered without opening a dashboard.

  • monitors
  • incidents
  • logs
  • metrics

Ask Elaichi to work across your apps.

Which monitors are alerting in production right now?

Summarize the open incidents from the last 24 hours.

Show error logs for the checkout service since midnight.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint reaches Datadog (US3) from every client.

Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

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

Tool catalog

352 Datadog (US3) tools, with no code written.

Logs, metrics, traces, monitors, incidents, hosts and notebooks, covered without writing a connector.

  • Search datadog events
  • Get datadog incident
  • Get datadog metric
  • Get datadog metric context
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.

Toolboxes

Each team gets its own Datadog (US3) toolbox.

On-call sees incidents and monitors, support sees logs, each scoped to what they need.

  • On-call
  • Platform
  • Backend
  • Frontend
ElaichiToolboxes
Name Source template Tools Created

On-call toolbox

Datadog (US3) · incidents and monitors

Datadog (US3) starter 18 Mar 4, 2026

Platform toolbox

Datadog (US3) · hosts and metrics

— 9 Mar 2, 2026

Backend toolbox

Datadog (US3) · traces and spans

— 24 Feb 27, 2026

Frontend toolbox

Datadog (US3) · RUM events and sessions

Datadog (US3) starter 6 Feb 19, 2026

Support toolbox

Datadog (US3) · logs and incidents

— 31 Jan 30, 2026

Leadership toolbox

Datadog (US3) · dashboards and notebooks

— 12 Jan 22, 2026

Shared connections

Teammates query Datadog (US3) without seeing a key.

One person connects, shares with teams, and nobody else ever handles an API key.

  • Production
  • Staging
  • On-call
  • Platform
ElaichiConnections
Connection Scope Status Access
DA

Datadog (US3) (Production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
DA

Datadog (US3) (Staging)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
DA

Datadog (US3) (On-call)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
DA

Datadog (US3) (Platform)

Connected by Tyler Reed

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

Datadog (US3) (Support)

Connected by Ryan Hayes

Personal • Active Not shared
DA

Datadog (US3) (Frontend)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Datadog (US3) call names who made it.

When, who, what happened and which monitor or log, kept in an append-only log.

  • When
  • Who
  • What happened
  • Type
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 (US3) Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Datadog (US3) Monitors Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Datadog (US3) Monitors List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule starts the incident digest itself.

Incidents are fetched, grouped, drafted into a digest, approved by a person, then posted back.

Datadog (US3) 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 (US3)

    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 Michael Brennan

    Approve
  6. Post the digest

    Datadog (US3)

    Queued

Collections and dashboards

Datadog (US3) health, counted without a model.

Four metrics, a 14 day chart of incidents, and a breakdown by team, refreshed on schedule.

Datadog (US3) 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%

On-call 21%

Platform 18%

FAQ

Frequently asked questions

How do I connect Datadog (US3) to Claude?

Connect Datadog in US3 inside Elaichi, where it signs in over OAuth, so you approve access in your Datadog account and there is no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi as yourself, and from then on it can read your Datadog US3 logs, monitors and incidents.

Does Datadog (US3) work with ChatGPT and Cursor as well as Claude?

Yes. Once Datadog in US3 is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi agent. You connect Datadog (US3) once and every client sees it.

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

With Datadog in US3 connected, an agent can search logs, metrics, traces, spans, hosts, events and RUM events, look up monitors and incidents, find dashboards, and create or edit notebooks. In practice that means asking which monitors are alerting, what the error logs say for a service, or for a summary of the open incidents. Short, specific asks work better than long sentences.

Does connecting Datadog (US3) give the AI access to everything in my organization?

No. Every call to Datadog in US3 runs as the person who signed in, so the AI sees only the logs, monitors, incidents and dashboards that person can already see in Datadog. Elaichi can narrow that further for a team or a role, and it never widens it.

Can my team share one Datadog (US3) connection?

Yes. One person connects Datadog in US3 and shares it with a team in Elaichi, and nobody else on the team ever handles an API key or application key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who searched the logs or edited a notebook in Datadog (US3).

Can I stop an agent from changing things in Datadog (US3)?

Yes. Restrictions in Elaichi apply per action, so you can let an agent search logs, metrics and incidents in Datadog (US3) while blocking it from creating or editing notebooks. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it. This connector has no action that deletes anything in Datadog in US3.

What happens to a Datadog (US3) connection when someone leaves?

Offboarding a person in Elaichi ends their access to Datadog in US3 at once, across Claude, ChatGPT, Cursor and every other client. A connection they shared with a team keeps working for everyone else. Disconnecting Datadog (US3) once in Elaichi removes it from every client at the same time.

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

Yes. Datadog (US3) 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, 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 (US3)?

Yes. Both let Claude, ChatGPT or Cursor use Datadog (US3). 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 (US3) call.

How is Elaichi different from Composio for Datadog (US3)?

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 (US3): 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 (US3) in front of your team

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

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.