# 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.

Source: https://elaichi.ai/connectors/datadog-ap1/

## Facts

| | |
| --- | --- |
| Application | Datadog (AP1) |
| Category | Observability |
| AI tools | 352 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Datadog (AP1) builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | help.datadoghq.com/hc/en-us |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Datadog (AP1) is connected

- 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.

## Connect Datadog (AP1) in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Datadog (AP1).
2. Optionally set Share with, then press Connect.
3. Approve it in Datadog (AP1). Datadog (AP1)'s own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Datadog (AP1) tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Datadog (AP1) MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Datadog (AP1) to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Datadog (AP1) tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Datadog (AP1) through Elaichi

### Get the picture during an incident

On-call. 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.

### Find the slow request after a deploy

Engineering. Ask which spans got slower in the last hour and have the agent set them beside the error logs for the same service.

### Check what a customer actually saw

Support. Look up the browser session events behind a reported problem and read the error logs tied to them before replying to the ticket.

### Write the postmortem notebook from the data

SRE. Create a notebook with the timeline, the monitors involved, and the metrics that mattered, then edit it as the review goes on.

### Review monitors before they go live

Platform. Check that a monitor definition is valid, start from a template, and see which monitor groups already cover a host.

### Answer a usage question without a dashboard

Product. Ask how many users hit a page or how an error rate moved over the week, straight from live metrics and user session events.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Datadog (AP1) connection?

Yes. One person connects Datadog in AP1 and shares it with a team in Elaichi, and nobody else handles an API key or application key. Each person still signs in to Elaichi as themselves, so the audit log names who asked for which logs or incidents.

### 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.

## All 352 Datadog (AP1) tools

Every tool below is callable through https://api.elaichi.ai/mcp once Datadog (AP1) is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Search datadog events** (Search). Searches events like monitor alerts, deployment notifications, infrastructure changes, security findings, and service status changes.
- **Get datadog incident** (Get). Retrieves detailed information about an incident.
- **Get datadog metric** (Get). Queries and analyzes historical or real-time metric data, supporting custom queries and aggregations.
- **Get datadog metric context** (Get). Retrieves detailed information about a metric including metadata, available tags, and tag values for filtering and grouping.
- **Search datadog monitors** (Search). Retrieves information about Datadog monitors, including their statuses, thresholds, and alert conditions.
- **Get datadog trace** (Get). Fetches a complete trace from Datadog APM using a trace ID.
- **Search datadog dashboards** (Search). Lists available Datadog dashboards and key details.
- **Get datadog notebook** (Get). Retrieves detailed information about a specific notebook by ID, including name, status, and author.
- **Search datadog notebooks** (Search). Lists and searches Datadog notebooks with filtering by author, tags, and content.
- **Search datadog hosts** (Search). Lists and provides information about monitored hosts, supporting filtering and searching.
- **Search datadog incidents** (Search). Retrieves a list of Datadog incidents, including their state, severity, and metadata.
- **Search datadog metrics** (Search). Lists available metrics, with options for filtering and metadata.
- **Search datadog entities** (Search). Searches Datadog's Catalog for service identity, ownership and upstream and downstream dependencies.
- **Search datadog spans** (Search). Retrieves spans from APM traces with filters such as service, time, resource, and so on.
- **Aggregate spans** (Action). Aggregates APM spans to compute counts, sums, averages, minimums, maximums, cardinality, and percentiles (p50 to p99). Group results by fields such as service or resource, or set `group_by.interval` in milliseconds to return a timeseries.
- **Analyze datadog logs** (Action). Analyze Datadog logs using SQL queries for counting, aggregations, and numerical analysis. Use this for statistical analysis.
- **Search datadog logs** (Search). Searches logs with filters (time, query, service, host, storage tier, and so on) and returns log details. Renamed from `get_logs`.
- **Search datadog rum events** (Search). Search Datadog RUM events using advanced query syntax.
- **Aggregate rum events** (Action). Aggregates RUM events to compute counts, sums, averages, min, max, cardinality, and percentiles, with grouping support. Use this for statistical analysis and trend data, not for inspecting individual events.
- **Create datadog notebook** (Create). Creates a new Datadog notebook.
- **Edit datadog notebook** (Action). Edits an existing Datadog notebook.
- **Validate datadog monitor** (Validate). Validates a monitor definition for correctness before creating or updating it.
- **Get datadog monitor templates** (Get). Retrieves available monitor templates to help you create monitors.
- **Search datadog monitor groups** (Search). Searches monitor groups by name or criteria.
- **Search datadog slos** (Search). Searches Datadog SLOs by name, tags, or type. Supports query syntax for filtering by service, team, or other attributes.
- **Create datadog monitor** (Create). Creates a Datadog monitor in draft mode. Monitors created with this tool do not send notifications and are set to priority 5 (low). Use `validate_datadog_monitor` to check the definition before creating and `get_datadog_monitor_templates` for query syntax examples. After…
- **Get monitor coverage** (Get). Finds monitoring gaps and coverage for services or hosts. Returns which signals (such as error rate, latency, and request rate) are covered by existing monitors and which are missing. Use with `create_datadog_monitor` to fill gaps.
- **Apm query trace** (Search). Runs a read-only SQL query against a trace's spans to answer a specific question, such as ranking spans by self-time or isolating one span's attributes. Complements `get_datadog_trace`, which shows a trace's overall shape.
- **Apm discover span tags** (Action). Discovers available tag keys on spans within a time range.
- **Apm get primary tag keys** (Get). Retrieves the primary tag keys configured for the organization.
- **Apm get service health** (Get). Retrieves the current health status (ok/warning/critical) for one or more APM services plus the signals driving it (paging monitors, incidents, Watchdog anomalies, DBM regressions). Returns present state only; no historical trends.
- **Apm latency bottleneck summary** (Action). Analyzes latency bottlenecks across traces in an anomaly period using self-time calculations. Identifies which service and resource combinations consume the most self-time, detects cascading call patterns, and surfaces root causes of latency spikes.
- **Apm search recommendations** (Search). Searches for APM recommendations from Datadog.
- **Apm get recommendation** (Get). Retrieves full details of a specific APM recommendation by ID.
- **Search apm sampling rules** (Search). Lists remote sampling rules that set a fixed sample rate for spans matching a service, environment, and resource. Filter by service, environment, or both.
- **Create apm sampling rule** (Create). Creates a remote sampling rule that sets a sample rate for a service, environment, and resource, with no redeploy needed. A low rate can drop most of a service's traces. If a rule already exists for that target, use `update_apm_sampling_rule` instead. The tool requires…
- **Update apm sampling rule** (Update). Changes the sample rate of an existing remote sampling rule, identified by its service, environment, and resource. To change the rule's target, delete the rule and create a new one. The tool requires explicit confirmation before it applies changes.
- **Delete apm sampling rule** (Delete). Permanently deletes a remote sampling rule, identified by its service, environment, and resource. Matching spans fall back to the next applicable sampling mechanism. The tool requires explicit confirmation before it deletes the rule. This operation is idempotent.
- **Search apm service remapping rules** (Search). Lists the organization's service remapping rules in evaluation order, or retrieves one rule by ID. Each result includes the rule's filter, new name, and current version.
- **Create apm service remapping rule** (Create). Creates a service remapping rule that renames services or inferred entities on matching spans, which changes how they appear across APM, monitors, and dashboards. New rules are evaluated after existing rules. You can also specify a different tag for the rule to rewrite. The…
- **Update apm service remapping rule** (Update). Updates an existing service remapping rule's name, filter, the name it assigns to matching services or inferred entities, or the tag it rewrites (`service` or `peer.service` by default). The rule type cannot be changed, and rules with multiple rewrite mappings must be edited…
- **Reorder apm service remapping rules** (Action). Sets the evaluation order of all service remapping rules. The first matching rule applies, so order determines which rule wins when a span matches more than one. The tool requires explicit confirmation before it applies changes.
- **Delete apm service remapping rule** (Delete). Permanently deletes a service remapping rule by ID. New spans that matched the rule keep their original service name. Data that's already indexed doesn't change. The tool requires explicit confirmation before it deletes the rule. This operation is idempotent.
- **Send message to assistant** (Send). Sends a message to the Datadog Assistant and returns its response. Optionally continues an existing conversation by providing a `conversation_id`.
- **Get assistant conversation history** (Get). Retrieves the full conversation history for a specific assistant conversation by its ID.
- **List assistant conversations** (List). Lists all Datadog Assistant conversations for the current user.
- **Search audit events** (Search). Searches for Audit Trail events using Datadog query syntax with support for pagination. Use when you need to find and filter events by specific attributes. Returns Audit Trail events without metadata and previous or new asset values unless requested.
- **List audit events** (List). Lists Audit Trail events over a time window with support for pagination and an optional query. Use to scan recent Audit Trail events. Returns Audit Trail events without metadata and previous or new asset values unless requested.
- **Build audit trail query** (Search). Translates a natural-language description into an Audit Trail query string. If you are uncertain of query syntax when searching Audit Trail events, use this tool first with a description of the events you would like to retrieve, then pass the returned query and timestamps…
- **Search datadog cases** (Search). Searches Work Management work items (cases) with filters including status, priority, project, and assignee. Supports time range filtering and pagination.
- ...and 302 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.