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.
In Elaichi
Connect Datadog (US3) once
-
Open Connections, choose Add connection, and pick Datadog (US3).
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
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
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.”
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.
| 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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch monitors
Datadog (US3)
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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 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
-
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.