Can I use Datadog as a CLI?

Yes. KosmoKrator exposes a Datadog CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Datadog through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Datadog tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Datadog credentials stored?

Datadog credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Datadog MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

monitoring

Datadog MCP Gateway for AI Agents

Expose Datadog tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

10 functions 6 read 4 write API key auth

Submit Datadog feedback View package source

Datadog MCP Gateway

Expose Datadog to MCP clients with `kosmokrator mcp:serve --integration=datadog`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server. The gateway exposes only the selected integration in the example below.

curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

kosmokrator mcp:gateway:install --integration=datadog --write=deny --json

{
  "mcpServers": {
    "kosmokrator-datadog": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=datadog",
        "--write=deny"
      ]
    }
  }
}

Serve Manually

kosmokrator mcp:serve --integration=datadog --write=deny

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names:

MCP tool	Source function	Type
`integration__datadog__datadog_list_monitors`	`datadog.datadog_list_monitors`	Read `read`
`integration__datadog__datadog_get_monitor`	`datadog.datadog_get_monitor`	Read `read`
`integration__datadog__datadog_create_monitor`	`datadog.datadog_create_monitor`	Write `write`
`integration__datadog__datadog_update_monitor`	`datadog.datadog_update_monitor`	Write `write`
`integration__datadog__datadog_delete_monitor`	`datadog.datadog_delete_monitor`	Write `write`
`integration__datadog__datadog_query_metrics`	`datadog.datadog_query_metrics`	Read `read`
`integration__datadog__datadog_list_dashboards`	`datadog.datadog_list_dashboards`	Read `read`
`integration__datadog__datadog_get_dashboard`	`datadog.datadog_get_dashboard`	Read `read`
`integration__datadog__datadog_post_event`	`datadog.datadog_post_event`	Write `write`
`integration__datadog__datadog_get_current_user`	`datadog.datadog_get_current_user`	Read `read`

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.