Datadog (US5) MCP connector
Datadog (US5) connects to Elaichi over OAuth so Claude, ChatGPT, Cursor, and any MCP client can search logs, monitors, incidents, traces, and dashboards as the person who signed in, with every call logged.
-
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 (US5) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Datadog (US5) once
-
Open Connections, choose Add connection, and pick Datadog (US5).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Datadog (US5). Datadog (US5)'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 (US5) 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 (US5) 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 (US5) 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 (US5) 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 (US5) through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
On-call
Find out what broke before the call starts
Ask for the open incidents and the monitors that fired in the last hour, then pull the matching logs and traces without opening six tabs.
-
Engineering
Chase a slow request through its traces
Pull the trace for a request, aggregate the spans around it, and see which service is holding things up.
-
Support
Check a customer's session before replying
Search RUM events for the customer's session and see the errors they hit, so the reply is about what actually happened.
-
Platform
Spot hosts that stopped reporting
Search hosts by tag or environment and ask which ones have gone quiet since the last deploy.
-
Engineering
Write the postmortem in a notebook
Get the incident, pull the timeline from events and logs, and create a notebook in Datadog that the team can edit afterward.
-
Security
Analyze logs for a suspicious pattern
Search and analyze logs for repeated failed logins or unusual source addresses, and summarize what the pattern looks like over the day.
Try asking
- “Which monitors fired on the checkout service in the last hour?”
- “Summarize the open incidents and who is assigned to each.”
- “Show error logs for api-gateway since the 9am deploy.”
Compare
Elaichi vs Zapier MCP vs Composio for Datadog (US5)
All three can connect Datadog (US5) 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 (US5) tools | Allow or restrict single Datadog (US5) 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 (US5) 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 (US5) tools for your AI agents
352 tools are ready to call through Elaichi's MCP endpoint the moment you connect Datadog (US5), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Datadog (US5) builds and runs these tools.
No tools match your search.
Showing 317 of 352 Datadog (US5) tools here. Connect Datadog (US5) and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Datadog (US5) gets you
6 screens from the product, each doing one job for your Datadog (US5) account.
The agent
Ask Datadog (US5) what is on fire.
Plain language questions, answered from live incidents, monitors, and logs in Datadog (US5).
- incidents
- monitors
- logs
- notebooks
Ask Elaichi to work across your apps.
Which monitors fired on the checkout service in the last hour?
Summarize the open incidents and who is assigned to each.
Show error logs for api-gateway since the 9am deploy.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Datadog (US5) to every client.
Claude, ChatGPT, and Cursor reach Datadog (US5) through one endpoint, no SDK, no shared API key.
Copy the endpoint
Tool catalog
352 Datadog (US5) tools, no code to write.
Logs, monitors, incidents, traces, dashboards, and notebooks, covered without writing a line of code.
- Search datadog events
- Get datadog incident
- Get datadog metric
- Get datadog metric context
Toolboxes
Every team gets its own Datadog (US5) toolbox.
On-call sees incidents and monitors, support sees RUM sessions, each team scoped to its work.
- On-call
- Platform
- Backend
- Frontend
Shared connections
Share Datadog (US5) without sharing a credential.
One person connects Datadog (US5), teams work through it, and nobody else sees a key.
- Production
- Staging
- Platform
- Security
Audit log
Every Datadog (US5) call names who made it.
When, who, what happened, and which incident or notebook, in one 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 drafts the Datadog (US5) digest.
Incidents fetched, grouped, drafted, approved by a person, then posted back to Datadog (US5).
Datadog (US5) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch incidents
Datadog (US5)
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 (US5)
Queued
Collections and dashboards
Datadog (US5) health numbers, computed without a model.
Incidents created over 14 days, by team, refreshed on a schedule, no asking required.
Datadog (US5) health
Refreshed 4 minutes ago · every 15 minutes · from the incidents collection
Incidents
1,284 ↓ 12%
Monitors
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Incidents created
Last 14 days
By team
Share of activity
Production 34%
Staging 27%
Platform 21%
Security 18%
FAQ
Frequently asked questions
How do I connect Datadog (US5) to Claude?
In Elaichi, choose Datadog (US5) and connect it. Datadog in US5 connects over OAuth, so you sign in to your Datadog account and approve access, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. That is the whole setup, and it takes a few minutes.
Does Datadog (US5) work with ChatGPT and Cursor as well as Claude?
Yes. Once Datadog in US5 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 (US5) once and every client picks it up.
What can an AI agent actually do with my Datadog (US5) data?
With Datadog in US5 connected, an agent can search logs, events, hosts, monitors, incidents, metrics, traces, spans, and RUM events, pull up a dashboard or notebook, and create or edit notebooks. It can also analyze logs and aggregate spans or RUM events to answer questions like which service is slowest this morning. Short, concrete asks such as "open incidents in the last six hours" work better than long paragraphs.
Does connecting Datadog (US5) give the AI access to everything in my Datadog organization?
No. Every call to Datadog in US5 runs as the person who signed in, so the agent sees only the logs, dashboards, monitors, and incidents that person can already see in Datadog. Elaichi can narrow that access further with restrictions, and it can never widen it.
Can I stop an agent from changing things in Datadog (US5)?
Yes. Restrictions in Elaichi apply per action, so you can allow searching logs, monitors, and incidents in Datadog (US5) while blocking notebook creation and edits. A restricted action is never advertised to Claude, ChatGPT, or Cursor, so no prompt can reach it in Datadog in US5.
What happens to a Datadog (US5) connection when someone leaves?
Offboarding that person in Elaichi ends their access to Datadog in US5 at once, in every client. A shared Datadog (US5) connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Datadog (US5) once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.
Does the Datadog (US5) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Datadog (US5) 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 (US5)?
Yes. Both let Claude, ChatGPT or Cursor use Datadog (US5). 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 (US5) call.
How is Elaichi different from Composio for Datadog (US5)?
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 (US5): 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 (US5) 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.