Digma Code Observability

Created By
Roni Dovera year ago
The Digma MCP Server uses a dynamic code analysis engine to leverage the data in your APM dashboards (Datadog, Grafana, NewRelic etc.) in order to assist the AI agent during code reviews, code and test generation, fix suggestions, etc. It enables the agent to drive performance improvements and cost reduction. Features: - Highlight risky code in the PR and provide impact visibility - Assess the proposed code based on real performance requirements - Highlight the code areas that would have the most impact when optimized - Automatically identify and fix performance bottlenecks, ineffcient queries, scaling problems and other issues
Overview

Digma MCP Server

A Model Context Protocol (MCP) server implementation for enabling agents to access observability insights using Digma for code observability and dynamic code analysis

Key Features 🚀

  • 🗣️ Observability-assisted code reviews: Check the PR branch for any issues discovered by pre-prod observability.
  • 🔎 Find code inefficiencies with dynamic code analysis: Identify issues in the code/queries that are slowing the app down
  • 🔭 Utilize code runtime usage data from distributed tracing: Check for breaking changes or generated relevant tests

Example prompts 💬

  • help me review the code changes in this branch by looking at related runtime issues
  • I want to improve the performance of this app. What are the three most severe issues I can fix?
  • I'm making changes to this function, based on runtime data. What other services and code would be affected?
  • Are there any new issues in this code based on the Staging environment?
  • Which database queries have the most impact on the application performance?

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Roni Dover
Star
-
Language
-
License
-
Category

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