datadog:setup

Configure Datadog credentials and verify MCP server connectivity.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/fabn/claude-plugins --skill datadog-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datadog:setup
Source: https://github.com/fabn/claude-plugins/tree/main/plugins/datadog/skills/setup
Command: npx skills add https://github.com/fabn/claude-plugins --skill datadog-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many projects lack a consistent Datadog configuration and valid API credentials, which causes failed monitoring queries, broken dashboards, and wasted time diagnosing connectivity issues. This Skill streamlines credential verification, MCP connectivity checks, and project-level default configuration so teams can reliably query logs, traces, and dashboards.

Core Features & Use Cases

  • Credential verification: Checks for DD_API_KEY, DD_APP_KEY, and DD_SITE in your local Claude settings and explains where to obtain missing values.
  • MCP connectivity tests: Discovers Datadog MCP tools and performs lightweight API calls to validate authentication and network reachability.
  • Project defaults: Prompts to set a default service and search filter and writes or updates an invisible configuration block in the project's CLAUDE.md for consistent query scoping.
  • Diagnostics and guidance: Provides targeted fixes for common failures such as missing keys, incorrect site, insufficient scopes, malformed JSON, or plugin installation issues.

Quick Start

Set up Datadog by verifying DD_API_KEY, DD_APP_KEY, and DD_SITE in your ~/.claude/settings.local.json, testing MCP connectivity, and optionally saving default service and filter settings to CLAUDE.md.

Frequently Asked Questions about datadog:setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Datadog credentials for my project to query logs and dashboards?

Datadog credential configuration requires setting DD_API_KEY, DD_APP_KEY, and DD_SITE in your ~/.claude/settings.local.json file, after which the setup process validates authentication through lightweight MCP API calls to confirm network reachability.

Why are my Datadog monitoring queries failing with authentication errors?

Datadog queries fail when DD_API_KEY or DD_APP_KEY are missing, the DD_SITE is incorrect, or API keys lack sufficient scopes. Use a diagnostic setup process to check local settings, validate credentials, and receive targeted fixes for these common failures.

What is the best way to set default service and search filters for Datadog queries?

The best way to set default service and search filters is to write or update an invisible configuration block in the project's CLAUDE.md file, ensuring consistent query scoping across logs, traces, and dashboards for the entire team.

Can I use the Datadog MCP server to verify API connectivity before running monitoring queries?

Yes, you can discover available Datadog MCP tools and perform lightweight API calls to verify API connectivity, validate credentials, and test network reachability before attempting to query logs, traces, or dashboards.

Do I need a specific settings file format to store Datadog API keys locally?

Yes, Datadog API keys must be stored in ~/.claude/settings.local.json as valid JSON. Malformed JSON in this settings file will cause authentication failures, and the setup process can diagnose and provide guidance on fixing the structure.