Datadog (AP1) MCP connector
The Datadog (AP1) connector brings logs, metrics, traces, monitors, incidents, and notebooks from Datadog's AP1 region to Claude, ChatGPT, Cursor, and the Elaichi Agent, so each person can ask about them under their own Datadog access.
-
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 (AP1) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Datadog (AP1) once
-
Open Connections, choose Add connection, and pick Datadog (AP1).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Datadog (AP1). Datadog (AP1)'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 (AP1) 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 (AP1) 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 (AP1) 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 (AP1) 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 (AP1) 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 during an incident
Pull up the incident in Datadog AP1, see which monitors fired, and read the logs and traces around it in one conversation instead of six tabs.
-
Engineering
Find the slow request after a deploy
Ask which spans got slower in the last hour and have the agent set them beside the error logs for the same service.
-
Support
Check what a customer actually saw
Look up the browser session events behind a reported problem and read the error logs tied to them before replying to the ticket.
-
SRE
Write the postmortem notebook from the data
Create a notebook with the timeline, the monitors involved, and the metrics that mattered, then edit it as the review goes on.
-
Platform
Review monitors before they go live
Check that a monitor definition is valid, start from a template, and see which monitor groups already cover a host.
-
Product
Answer a usage question without a dashboard
Ask how many users hit a page or how an error rate moved over the week, straight from live metrics and user session events.
Try asking
- “Which monitors fired for the checkout service in the last hour?”
- “Summarize the open incidents in Datadog (AP1) for the standup.”
- “Show error logs for api-gateway since the 9am deploy.”
Compare
Elaichi vs Zapier MCP vs Composio for Datadog (AP1)
All three can connect Datadog (AP1) 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 (AP1) tools | Allow or restrict single Datadog (AP1) 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 (AP1) 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 (AP1) tools for your AI agents
352 tools are ready to call through Elaichi's MCP endpoint the moment you connect Datadog (AP1), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Datadog (AP1) builds and runs these tools.
No tools match your search.
Showing 317 of 352 Datadog (AP1) tools here. Connect Datadog (AP1) and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Datadog (AP1) gets you
6 screens from the product, each doing one job for your Datadog (AP1) account.
The agent
Ask Datadog (AP1) what is happening right now.
Plain questions, answered from live logs, monitors, and incidents in Datadog (AP1).
- logs
- monitors
- incidents
- notebooks
Ask Elaichi to work across your apps.
Which monitors fired for the checkout service in the last hour?
Summarize the open incidents in Datadog (AP1) for the standup.
Show error logs for api-gateway since the 9am deploy.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint for Claude, ChatGPT, and Cursor.
Every client reaches Datadog (AP1) through one governed endpoint, no SDK and no shared API key.
Copy the endpoint
Tool catalog
352 Datadog (AP1) tools, no code to write.
Logs, metrics, traces, monitors, incidents, hosts, and notebooks covered out of the box.
- Search datadog events
- Get datadog incident
- Get datadog metric
- Get datadog metric context
Toolboxes
Every team gets its own Datadog (AP1) toolbox.
Scope on-call, support, and security to the Datadog (AP1) tools their work needs.
- On-call
- Engineering
- Support
- Security
Shared connections
Share a Datadog (AP1) account, not its keys.
Teammates search logs and incidents through one connection without ever seeing a credential.
- On-call
- Backend
- Support
- Security
Audit log
Know who looked at which Datadog (AP1) logs.
Every query, by whom, when, and on what, 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
Schedules start the incident digest, not prompts.
Fetch Datadog (AP1) incidents, group them, draft a digest, approve, post back.
Datadog (AP1) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch logs
Datadog (AP1)
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 (AP1)
Queued
Collections and dashboards
Datadog (AP1) health numbers, computed without a model.
Four metrics, 14 days of incidents created, and a breakdown by team, refreshed on schedule.
Datadog (AP1) health
Refreshed 4 minutes ago · every 15 minutes · from the logs collection
Logs
1,284 ↓ 12%
Monitors
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Logs created
Last 14 days
By team
Share of activity
On-call 34%
Backend 27%
Support 21%
Security 18%
FAQ
Frequently asked questions
How do I connect Datadog (AP1) to Claude?
Open Elaichi, pick Datadog (AP1), and sign in to your Datadog AP1 account when it asks, the same login you already use, with no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it answers questions from your Datadog AP1 logs, monitors, and incidents.
Does Datadog (AP1) work with ChatGPT and Cursor as well as Claude?
Yes. Datadog in AP1 is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent. There is nothing extra to set up for each client.
What can an AI agent actually do with my Datadog (AP1) data?
It can search logs, metrics, traces, spans, events, hosts, monitors, incidents, dashboards, and browser session events in Datadog AP1, then sum up what it finds in plain language. It can also create and edit notebooks, check that a monitor definition is valid, and pull monitor templates. Short, specific asks work best, for example errors for the checkout service in the last hour rather than a long paragraph.
Does connecting Datadog (AP1) give the AI access to everything in my organization?
No. The agent sees only what you can see in Datadog AP1 under your own login, so Datadog's roles and restricted queries still apply. Elaichi can narrow that further, for example to read-only questions, but it can never widen it beyond what Datadog already lets you do.
Can I stop an agent from creating or changing things in Datadog (AP1)?
Yes. In Elaichi, restrictions on the Datadog (AP1) connector work per action, so you can allow searching logs and metrics but block creating or editing notebooks. A restricted action is never shown to Claude or any other client, so no prompt can reach it.
What happens to a Datadog (AP1) connection when someone leaves?
Offboarding the person in Elaichi ends their access to Datadog in AP1 at once, in every client they used. A connection they shared keeps working for everyone else on the team. Disconnecting Datadog (AP1) once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.
Does the Datadog (AP1) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Datadog (AP1) 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 (AP1)?
Yes. Both let Claude, ChatGPT or Cursor use Datadog (AP1). 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 (AP1) call.
How is Elaichi different from Composio for Datadog (AP1)?
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 (AP1): 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 (AP1) 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.