Dash0
Official Model Context Protocol (MCP) server for Dash0 that enables AI assistants to navigate OpenTelemetry resources, investigate incidents, and query metrics, logs, and traces within the Dash0 observability platform. Deployed as a remote HTTP endpoint using Streamable HTTP transport.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
HTTPS required for Streamable HTTP transport. Bearer token auth with dataset-scoped permissions provides reasonable isolation. Secret handling appears sound (env vars in config examples), but deployment guidance is minimal. Low dependency_hygiene score due to unknown upstream dependencies and lack of supply chain transparency in sparse repo documentation. Early-stage project (June 2025 creation) may not have undergone security audit.
⚡ Reliability
Best When
You need AI-assisted observability access within Dash0 or are building AI-native incident response workflows that require real-time metrics, logs, and traces integration.
Avoid When
You need local-only deployment, don't have Dash0 subscription, or require alternative observability platforms (Datadog, Grafana, New Relic).
Use Cases
- • AI-assisted incident investigation in Dash0
- • Querying metrics, logs, and traces via natural language
- • Navigating OpenTelemetry resource hierarchies
- • Integrating Dash0 observability into AI assistants (Claude, Cline, Cursor, Windsurf)
- • Automated incident analysis workflows
Not For
- • Direct local installation (requires remote HTTP endpoint)
- • Clients without Streamable HTTP transport support (though npx mcp-remote wrapper is provided)
- • Air-gapped environments requiring local deployment
Interface
Authentication
Uses Dash0 auth tokens with configurable permissions per dataset. Token created in Dash0 app requires explicit permissions on datasets. Bearer token passed in Authorization header. Simple key-based auth model.
Pricing
No separate MCP server pricing; requires active Dash0 subscription and app account.
Agent Metadata
Known Gotchas
- ⚠ Remote HTTP endpoint requires network connectivity and Dash0 uptime
- ⚠ Streamable HTTP transport not yet implemented in all MCP clients (npx mcp-remote wrapper required for compatibility)
- ⚠ Auth token scoping tied to datasets; agent access limited by token permissions
- ⚠ No documented rate limits, retry guidance, or error recovery patterns
- ⚠ Sparse documentation on available tools/operations the MCP server exposes
- ⚠ Created 2025-06-23 with minimal GitHub activity (2 stars, 1 fork) suggests early-stage/experimental status
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Dash0.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.