Sentry & Datadog APM Observability MCP Profile
AI-generated MCP configuration example referring to Sentry and Datadog. Verify that the named servers exist and provide the requested API capabilities.
Tags: mcp, sentry, datadog, observability, apm, logs, error-tracking
Category: devops
Listing attribution: SimplyUtils
Before using this resource
Attribution and license labels come from the listing metadata. Check the source and its license before redistributing or adapting files. This listing has no documented license; do not assume permission to redistribute it.
Read instructions before adding them to an agent or project. Test a small, non-confidential example and inspect the result. A downloaded instruction file may refer to scripts, templates, or other files that are not included here.
SimplyUtils supplied this template, which was generated by an AI agent using an LLM. It is an example to inspect and adapt, not a verified package or a record of expert testing. Check named dependencies, commands, permissions and generated results before use. Redistribution terms for this template have not been verified; licenses for third-party software are separate.
Sentry & Datadog APM Observability MCP Profile
Overview
Connect your AI agent directly to Sentry issue tracking and Datadog APM logs using this MCP server profile. Agents can pull production unhandled exception traces, correlate error frequencies with recent releases, and suggest immediate code patches.
MCP Configuration (mcp_config.json)
{
"mcpServers": {
"sentry-observability": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-sentry"],
"env": {
"SENTRY_AUTH_TOKEN": "sntrys_your_read_only_token",
"SENTRY_ORG": "your-org-slug"
}
},
"datadog-logs": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-datadog"],
"env": {
"DATADOG_API_KEY": "your_dd_api_key",
"DATADOG_APP_KEY": "your_dd_app_key",
"DATADOG_SITE": "datadoghq.com"
}
}
}
}
Recommended Diagnostic Workflow
1. Fetch latest high-impact production issue from Sentry: sentry_get_latest_issues({ limit: 5 }).
2. Inspect exact stack trace lines and affected file paths.
3. Locate corresponding source file in repository.
4. Draft root cause analysis and propose fix.