Datadog (UK1) MCP connector
Connect Datadog (UK1) to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can search its logs, metrics, monitors, incidents, traces and dashboards, with each person signed in as themselves and 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 (UK1) to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Datadog (UK1) once
-
Open Connections, choose Add connection, and pick Datadog (UK1).
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Datadog (UK1). Datadog (UK1)'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 (UK1) 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 (UK1) 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 (UK1) 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 (UK1) 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 (UK1) 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 during an incident
Pull up the open incident in Datadog, then search the logs, events and traces from the minutes before it started. Ask what changed and get an answer drawn from the live records rather than from memory.
-
SRE
Review the monitors watching a service
Search the monitors and monitor groups covering a service, see which are in alert, and check a new monitor definition against the templates before it is saved.
-
Support
Check the logs behind a customer ticket
Search the logs and real user monitoring events for the customer's session while the ticket is still open, so the reply to them is based on what actually happened.
-
Product
See how real users experienced a release
Aggregate real user monitoring events by page, browser or country for the day after a release and compare them with the week before.
-
Engineering
Write the postmortem in a notebook
Create a Datadog notebook for the incident, pull in the metrics, events and spans that tell the story, and edit it as the review fills in the gaps.
-
Platform
Find the hosts and services behind an alert
Search hosts and service entities when a monitor fires, get the context on the metric that tripped it, and see which dashboards already cover that part of the system.
Try asking
- “Which monitors are alerting on the checkout service right now?”
- “Show me the error logs from the last hour for api-gateway.”
- “Summarize the open incidents and who is handling each.”
Compare
Elaichi vs Zapier MCP vs Composio for Datadog (UK1)
All three can connect Datadog (UK1) 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 (UK1) tools | Allow or restrict single Datadog (UK1) 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 (UK1) 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 (UK1) tools for your AI agents
352 tools are ready to call through Elaichi's MCP endpoint the moment you connect Datadog (UK1), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Datadog (UK1) builds and runs these tools.
No tools match your search.
Showing 317 of 352 Datadog (UK1) tools here. Connect Datadog (UK1) and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Datadog (UK1) gets you
6 screens from the product, each doing one job for your Datadog (UK1) account.
The agent
Ask Datadog (UK1) a question in plain language.
Get answers from live logs, monitors and incidents without opening a single dashboard.
- monitors
- incidents
- logs
- notebooks
Ask Elaichi to work across your apps.
Which monitors are alerting on the checkout service right now?
Show me the error logs from the last hour for api-gateway.
Summarize the open incidents and who is handling each.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Use Datadog (UK1) from any MCP client.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
352 Datadog (UK1) tools, ready without code.
Logs, metrics, traces, monitors, incidents, dashboards and notebooks covered without writing custom code.
- Search datadog events
- Get datadog incident
- Get datadog metric
- Get datadog metric context
Toolboxes
Each team gets its own Datadog (UK1) toolbox.
On-call, SRE and Support each see only the tools their work needs.
- On-call
- SRE
- Support
- Product
Shared connections
Share Datadog (UK1) without sharing a credential.
One person connects, teammates work through it, and nobody else ever sees the key.
- Production UK
- Staging
- Platform
- On-call
Audit log
Every Datadog (UK1) call is on record.
When, who, what happened and which resource, in a log nobody can edit.
- 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 turns Datadog (UK1) incidents into a digest.
Incidents are fetched, grouped and drafted, a person approves, and the notebook posts back.
Datadog (UK1) digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch monitors
Datadog (UK1)
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 (UK1)
Queued
Collections and dashboards
Datadog (UK1) health numbers, computed without a model.
Four metrics, fourteen days of incidents created and a breakdown by team, refreshed on schedule.
Datadog (UK1) 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 UK 34%
Staging 27%
Platform 21%
On-call 18%
FAQ
Frequently asked questions
How do I connect Datadog (UK1) to Claude?
Two steps. In Elaichi, choose Datadog (UK1), click connect, and sign in to your Datadog UK1 account over OAuth, which takes you to the Datadog sign-in page and back. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp.
Does Datadog (UK1) work with ChatGPT and Cursor as well as Claude?
Yes. Once Datadog in UK1 is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Datadog once and every client you use picks it up.
What can an AI agent actually do with my Datadog (UK1) data?
An agent connected to Datadog in UK1 can search your logs, metrics, events, traces, spans, hosts, monitors, incidents, dashboards and real user monitoring events, and summarize what it finds. It can also create and edit notebooks and check a monitor definition before it is saved. Short, concrete asks such as "errors on checkout in the last hour" work better than long paragraphs.
Does connecting Datadog (UK1) give the AI access to my whole Datadog organization?
No. Every call to Datadog in UK1 runs as the person who signed in, so the agent sees only the logs, monitors and dashboards that person can already see in Datadog. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Datadog itself allows that person.
Can I stop an agent from changing things in Datadog (UK1)?
Yes. Restrictions in Elaichi apply per action, so you can allow searching logs, metrics and incidents in Datadog UK1 while blocking the actions that write, such as creating or editing a notebook. A restricted action is never shown to Claude, ChatGPT, Cursor or any other client, so no prompt can reach it.
What happens to a Datadog (UK1) connection when someone leaves?
Offboarding that person in Elaichi ends their access to Datadog in UK1 at once, across every client they used. A connection they shared with the team keeps working for everyone else. Disconnecting Datadog (UK1) once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Datadog (UK1) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Datadog (UK1) 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 (UK1)?
Yes. Both let Claude, ChatGPT or Cursor use Datadog (UK1). 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 (UK1) call.
How is Elaichi different from Composio for Datadog (UK1)?
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 (UK1): 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 (UK1) 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.