digma

The Digma MCP Server integrates Digma's observability and dynamic code analysis capabilities into your MCP workflow. It exposes an SSE endpoint that agents and clients can subscribe to for runtime insights, issue detection, and performance signals related to code changes. The server is designed to help agents review changes by cross-referencing observability data with the modified code, surfacing runtime issues, performance hotspots, and related tests to inform decision making during code reviews and deployments.

To use it, configure your MCP client to point at the Digma SSE URL or bridge it via a tool like SuperGateway. If you prefer a direct SSE connection, provide the URL in your MCP client configuration as shown in the README example. If you want to bridge it as a command tool, you can run it through npx with SuperGateway, which allows you to invoke the MCP server like a normal tool within your automation or editor environment. Once connected, agents can query runtime signals, inspect changed code paths, and request targeted analyses such as the most expensive queries, failing traces, or changes likely to impact performance.

Prerequisites:

• Node.js and npm installed on your machine (Node.js 14+ recommended).
• Access to the internet to install npm packages or to run npx commands.

Option A: Run via npx (no local installation required)

1. Ensure you have an API URL and token from Digma for your MCP setup. Replace placeholders in the command below.
2. Start the MCP bridge using npx:

npx -y supergateway --sse https://<DIGMA_API_URL>/mcp/DIGMA_API_TOKEN>/sse

Option B: Local install of the SuperGateway bridge (optional)

1. Install the required package globally or in your project:

npm install -g supergateway

2. Run the bridge with the SSE URL:

supergateway --sse https://<DIGMA_API_URL>/mcp/DIGMA_API_TOKEN>/sse

Prerequisites recap:

• Access to Digma MCP via API URL and token
• Node.js and npm installed
• Optionally, SuperGateway if you want to bridge to the MCP SSE via a command tool

Tips and considerations:

• The SSE URL uses your Digma API URL and token; keep these credentials secure and do not expose them in public repos.
• If you switch from SSE to a command-bridge approach, ensure your CI environment can run npx or has network access to fetch the required package.
• The mcp_config example uses a placeholder URL; replace DIGMA_API_URL and DIGMA_API_TOKEN with your actual values before running.
• If you encounter connectivity issues, verify that your environment allows outbound HTTPS traffic to the Digma API host and that your token has the necessary scopes for MCP access.