Spring Boot Runtime Diagnostics

io.github.neilmorsePublished by GitHub account neilmorsev0.2.12Updated Nov 3, 2026

Read-only Spring Boot runtime evidence for agents: beans, routes, health, startup.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

Spring Boot Runtime Diagnostics's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Spring Boot Runtime Diagnostics in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Spring Boot Runtime Diagnostics MCP

Chinese README

Give your coding assistant access to what is actually running in a Spring Boot application. This MCP server reads authorized Actuator and OpenAPI data to help investigate Beans, routes, health, database migrations and startup problems.

What can it check?

Your questionWhat it provides
Why was a Bean not created?Beans, dependencies and condition reports, with blocking chains when evidence is sufficient
Is this route registered?Actual paths, HTTP methods, Controllers and MVC/WebFlux mappings
What is unhealthy?Visible components and liveness/readiness status
Did a migration fail?Reported Flyway/Liquibase records, states and checksums
What made startup slow?Slow steps and their parent chains
Where did a configuration value come from?Sources for registered properties; configuration diagnostics require opt-in
Is this API in OpenAPI?Operations, schemas and references within the document
Does the process match my expectations?Compare the Bean, route, migration version and profile expectations you supply

For example, ask: “Check whether GET /orders/{id} is registered and tell me which Controller handles it.” The server reads mapping metadata without calling the business endpoint.

Get started

You need Python 3.11+, uv and an authorized local Spring Boot application. Confirm its management endpoints and permissions using the target setup guide, then check and start 0.2.12 Alpha:

bash
uvx --default-index https://pypi.org/simple spring-runtime-mcp==0.2.12 --versionuvx --default-index https://pypi.org/simple spring-runtime-mcp==0.2.12 --base-url http://127.0.0.1:18081

Use the second command as your MCP client's STDIO server command. In a terminal it waits for client requests. Follow the English first-query guide; additional client configuration templates cover other clients.

Try the synthetic route demo using the public package without preparing an application, then share first-query feedback. The replay needs no Spring process and does not establish live application or client compatibility.

Boundaries

The server connects only to loopback addresses, uses fixed endpoints and supports optional Bearer authentication from a named environment variable. OpenAPI uses /actuator/openapi. Configuration diagnostics are disabled by default and require explicit opt-in via CLI flags (--config-prefix, --config-property, --config-profiles). When enabled, values remain hidden unless both --config-allow-values and the tool’s includeValues=true are set. Output is sanitized, and each tool response is capped at 16 KiB. Missing evidence is reported as partial/unknown.

Tools do not write to the target, restart applications, or read heap dumps or raw logs. The complete Boot/Java/client matrix, Windows/macOS and production-cluster compatibility remain unverified.

Documentation · Tool contract · Source facts · Development and checks

Apache-2.0 · Contributing · Report a security issue

Source: README.md at commit f2e334f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

6
  1. v0.2.12LatestNov 3, 2026
  2. v0.2.8Nov 1, 2026
  3. v0.2.6Nov 1, 2026
  4. v0.2.4Nov 1, 2026
  5. v0.2.2Oct 31, 2026
  6. v0.2.1Oct 31, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts