bitDive/mcp-server

View on GitHub ↗

BitDive Model Context Protocol (MCP) server. The Autonomous Quality Loop for AI agents. Provides real runtime context, before/after trace comparison, and integration testing workflows.

77 ★18 forksPythonUpdated 3mo ago

What you need to know

Spring Boot MCP server exposing BitDive monitoring system data to AI agents: call traces, service maps, heap maps and error analysis.

Install

JDK 17+ and Maven required
./mvnw clean package && ./mvnw spring-boot:run

Usage

  • Connect an MCP client to the SSE endpoint http://localhost:8089/sse and message endpoint http://localhost:8089/mcp/message
  • For BitDive Cloud add {"mcpServers":{"bitdive":{"url":"https://cloud.bitdive.io/mcp/sse","name":"BitDive MCP Server"}}}
  • Obtain an API token from the BitDive dashboard MCP Integration section and add a user rule passing it to the AI

Key features

  • Trace tools: findTraceAll, findTraceForMethod, findTraceForMethodBetweenTime
  • Monitoring tools: getCurrentHeapMapAllSystem, per-module/service/class heap maps, getLastCallService
  • Spring Boot 3.2.0 with Spring AI 1.0.0 MCP Server WebFlux
  • PostgreSQL storage with HashiCorp Vault and Bouncy Castle security

Best for

AI assistants querying BitDive APM traces and performance heat maps.

Caveats

  • Current authentication requires passing the API key via prompts/rules; one-click integration is not yet available
  • Requires a running BitDive platform instance (self-hosted infrastructure or cloud)
  • Self-hosting needs configuration of POSTGRES_URL, POSTGRES_USER, POSTGRES_PASS, VAULT_URL and TOKEN_SECRET
Clients: Cursor · Claude
Documentation ↗

Reviewed 2026-08-11

Topics

ai-agentsbitdivellm-toolsmcpmcp-servermodel-context-protocolobservabilitypythontrace-analysistrace-analysis-tool
Stars
77★
Forks
18
Language
Python
License
Created
2025-10-03
Last push
2026-05-30