Datadog (AP2) MCP connector
The Datadog (AP2) connector lets Claude, ChatGPT, Cursor and the Elaichi Agent search the logs, metrics, traces, monitors, incidents and notebooks in your AP2 Datadog account, with every request signed in as the person asking.
-
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 (AP2) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Datadog (AP2) once
-
Open Connections, choose Add connection, and pick Datadog (AP2).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Datadog (AP2). Datadog (AP2)'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 (AP2) 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 (AP2) 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 (AP2) 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 (AP2) 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 (AP2) through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
SRE
Find out why a monitor is alerting
Ask which monitors are alerting, pull the metric behind the alert and the recent logs for the affected host, and get a plain summary of what changed.
-
On-call
Catch up on an incident at handover
Get the current state of an open incident, the events around it and the spans that look slow, then write the handover note into a notebook.
-
Platform engineering
Check a monitor definition before saving it
Validate a new monitor against the AP2 account and compare it with the monitor templates and monitor groups already in use.
-
Support
Look up what a customer actually experienced
Search RUM events for a customer's session and the logs from the same minutes, so the reply to the ticket is based on what happened rather than a guess.
-
Engineering
Trace a slow request end to end
Fetch a trace by id, aggregate the spans by service and spot the hop that is taking the time.
-
Engineering management
Write the weekly reliability digest
Search last week's incidents, group them by service and severity, and draft a notebook that the team reviews before it goes out.
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 this morning.”
Compare
Elaichi vs Zapier MCP vs Composio for Datadog (AP2)
All three can connect Datadog (AP2) 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 (AP2) tools | Allow or restrict single Datadog (AP2) 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 (AP2) 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 (AP2) tools for your AI agents
352 tools are ready to call through Elaichi's MCP endpoint the moment you connect Datadog (AP2), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Datadog (AP2) builds and runs these tools.
No tools match your search.
Showing 317 of 352 Datadog (AP2) tools here. Connect Datadog (AP2) and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Datadog (AP2) gets you
6 screens from the product, each doing one job for your Datadog (AP2) account.
The agent
Ask about alerts and get live answers.
Plain questions return monitors, logs and incidents straight from Datadog (AP2).
- incidents
- monitors
- logs
- notebooks
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 this morning.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint serves every AI client.
Claude, ChatGPT and Cursor reach Datadog (AP2) through one governed org endpoint, no shared API key.
Copy the endpoint
Tool catalog
352 tools cover Datadog (AP2) without code.
Logs, metrics, traces, monitors, incidents and notebooks, ready the moment you connect.
- Search datadog events
- Get datadog incident
- Get datadog metric
- Get datadog metric context
Toolboxes
Each team gets its own toolbox.
SRE, support and platform teams each see the Datadog (AP2) tools they need.
- SRE
- Platform engineering
- Backend engineering
- Frontend engineering
Shared connections
Share the connection, never the credential.
One person connects Datadog (AP2) and teammates work through it without seeing a secret.
- Production
- Staging
- SRE
- Platform
Audit log
Every query is on the record.
Who searched which logs, when, and on which host, 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.
Incidents are fetched, grouped and drafted, then a person approves before it posts to Datadog (AP2).
Datadog (AP2) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch incidents
Datadog (AP2)
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 (AP2)
Queued
Collections and dashboards
Reliability numbers arrive without asking.
Incidents, monitors and alerts from Datadog (AP2), computed on a schedule with no model involved.
Datadog (AP2) 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%
SRE 21%
Platform 18%
FAQ
Frequently asked questions
How do I connect Datadog (AP2) to Claude?
Connect Datadog in AP2 inside Elaichi first: you are sent to Datadog's own sign-in page for the AP2 region, you sign in and approve access, and you are done. There is 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.
Does Datadog (AP2) work with ChatGPT and Cursor as well as Claude?
Yes. Datadog in AP2 is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Each client signs people in over OAuth, so nobody pastes a key into a chat window.
What can an AI agent actually do with my Datadog (AP2) data?
An agent connected to Datadog in AP2 can search logs, metrics, traces, spans, hosts, events, monitors, dashboards and incidents, aggregate spans and RUM events, check a monitor definition before it is saved, and create or edit notebooks. It cannot change monitors, resolve incidents or delete anything through this connector. Short, specific asks such as "error logs for checkout since 9am" work better than long paragraphs.
Does connecting Datadog (AP2) give the AI access to the whole account?
No. Every request to Datadog in AP2 runs as the person who signed in, so the agent sees the organizations, logs and dashboards that person can already open in Datadog and nothing more. Elaichi can narrow that further with restrictions, and it can never widen it beyond what Datadog itself allows.
Can I stop an agent from changing things in Datadog (AP2)?
Yes. Restrictions in Elaichi apply per action, so you can allow searching logs, metrics and incidents in Datadog in AP2 while blocking the creation and editing of notebooks. A restricted action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.
What happens to a Datadog (AP2) connection when someone leaves?
Offboarding a person in Elaichi ends their access to Datadog in AP2 at once, across every client they used. A connection they shared keeps working for everyone else on the team. If you want the account gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the Datadog (AP2) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Datadog (AP2) 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 (AP2)?
Yes. Both let Claude, ChatGPT or Cursor use Datadog (AP2). 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 (AP2) call.
How is Elaichi different from Composio for Datadog (AP2)?
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 (AP2): 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 (AP2) 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.