datadog-mcp-server

Created By
i524a year ago
MCP Server for Datadog
Overview

what is datadog-mcp-server?

The datadog-mcp-server is a server application designed to work with Datadog, a monitoring and analytics platform for developers and IT operations. This project allows users to set up a server that can send metrics and events to Datadog.

how to use datadog-mcp-server?

To use the datadog-mcp-server, you need to install the dependencies using the command bun install, and then run the server with bun run src/index.ts. Make sure to set your Datadog API and APP keys in the environment variables.

key features of datadog-mcp-server?

  • Easy integration with Datadog for monitoring applications.
  • Built using Bun, a fast JavaScript runtime.
  • Supports sending metrics and events to Datadog.

use cases of datadog-mcp-server?

  1. Monitoring application performance in real-time.
  2. Collecting and visualizing metrics from various services.
  3. Setting up alerts based on specific metrics or events.

FAQ from datadog-mcp-server?

  • What is required to run the datadog-mcp-server?

You need to have Bun installed and your Datadog API and APP keys.

  • Is there a license for this project?

Yes, it is licensed under the MIT license.

  • Can I contribute to the datadog-mcp-server?

Yes, contributions are welcome on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
i524
Star
0
Language
TypeScript
License
MIT license
Category
monitoring

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