Datadog MCP Server

Created By
GeLi2001a year ago
Overview

what is Datadog MCP Server?

Datadog MCP Server is a Model Context Protocol (MCP) server designed for interacting with the Datadog API, enabling users to access and manage various monitoring and logging functionalities.

how to use Datadog MCP Server?

To use the Datadog MCP Server, install it via npm or from source, configure it with your Datadog API and application keys, and run it to interact with Datadog's services.

key features of Datadog MCP Server?

  • Monitoring: Access monitor data and configurations
  • Dashboards: Retrieve and view dashboard definitions
  • Metrics: Query available metrics and their metadata
  • Events: Search and retrieve events within timeframes
  • Logs: Search logs with advanced filtering and sorting options
  • Incidents: Access incident management data
  • API Integration: Direct integration with Datadog's v1 and v2 APIs
  • Comprehensive Error Handling: Clear error messages for API and authentication issues

use cases of Datadog MCP Server?

  1. Monitoring application performance and health
  2. Retrieving and analyzing logs for troubleshooting
  3. Managing incidents and alerts effectively
  4. Integrating with other tools for enhanced monitoring capabilities

FAQ from Datadog MCP Server?

  • What are the prerequisites for using Datadog MCP Server?

You need Node.js (version 16 or higher) and a Datadog account with API and application keys.

  • How do I install Datadog MCP Server?

You can install it via npm using npm install -g datadog-mcp-server or clone the repository and build it from source.

  • What should I do if I encounter a 403 Forbidden error?

Verify that your API key and Application key are correct and have the necessary permissions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
GeLi2001
Star
3
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago