spring-runtime-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPRING_RUNTIME_TIMEOUT | No | Per-request timeout in seconds for calls to the target Actuator endpoints. | 5 |
| SPRING_RUNTIME_BASE_URL | No | Origin (scheme, host, port) of the registered Spring Boot Actuator target. Registered once at startup; tool calls cannot override it. | http://127.0.0.1:18081 |
| SPRING_RUNTIME_TARGET_ID | No | Identifier for the registered target, used by tools to reference it. | local |
| SPRING_RUNTIME_SOURCE_CATALOG | No | Path to an operator-supplied source catalog used for conditional/bean blocking-chain analysis. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| springboot_analyze_startupA | 返回非破坏性启动快照中的版本、时间线跨度、最慢步骤及父子链；排查慢启动时调用，不用于当前请求延迟，也不执行排空缓冲区的 POST。 |
| springboot_check_migrationsB | 返回所有容器和迁移 Bean 的已报告迁移、校验和、顺序及异常状态；排查迁移失败或版本差异时调用，未报告的待执行状态需要可信预期，且不会执行 SQL 或迁移。 |
| springboot_detect_driftA | 比较调用者从获权工作区提取的 Bean、路由、迁移版本和 Profile 预期，返回差异及分级根因候选；源码与运行行为不一致时调用，省略维度不参与比较，文件时间本身不能证明未重启。 |
| springboot_diagnose_healthA | 返回整体健康状态、异常组件树及已脱敏的结构化错误和修复代码；依赖故障或探针异常时调用，组件下钻在本地完成，不获取日志、堆转储或原始异常栈。 |
| springboot_inspect_beansA | 返回匹配 Bean、别名及双向依赖图，并在 Bean 缺失时自动读取已授权条件报告、展开嵌套与传递阻塞链；排查注入或条件装配时调用，证据不足时返回 unknown，不猜测确切原因。 |
| springboot_inspect_configA | 返回双层强制脱敏后的生效属性、绑定 Bean、来源位置及 Active Profiles；排查属性绑定或配置覆盖时按前缀或键模式调用，能力默认关闭且不能用于获取秘密或导出全量配置。 |
| springboot_search_openapiB | 返回匹配操作或 Schema，并默认内联直接与二阶同文档引用；确认接口契约时使用精确选择器调用，不执行业务接口、不返回全量文档，也不解析远程引用。 |
| springboot_verify_mappingsA | 返回统一的 MVC/WebFlux 路由、处理器和方法描述符；排查路径、方法或 Controller 未注册时调用，不向业务 URL 发请求，也不把注册匹配等同于请求一定成功。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct diagnostic dimension (health, startup, migrations, drift, beans, config, OpenAPI, mappings), and descriptions add clear boundaries such as 'not for current request latency' or 'does not execute SQL'. The only real overlap is springboot_detect_drift, which compares beans/routes/migrations/profiles and thus partially duplicates inspect_beans, verify_mappings, and check_migrations, though its expectation-diff framing distinguishes it.
All eight tools follow the same springboot_<verb>_<noun> pattern with consistent verb choice (diagnose, analyze, check, detect, inspect, search, verify). No casing or style deviations.
Eight tools is well within the ideal 3-15 range and each maps to a distinct Spring runtime diagnostic concern. No filler or redundant tools are present.
The surface covers the core runtime diagnostic lifecycle: health, startup timing, migrations, bean graph, config, route registration, contract lookup, and drift comparison. Gaps exist (no metrics, scheduled tasks, filters/security chain, connection pools, or log/thread-dump access), but the latter are explicitly out of scope by design, leaving only minor workarounds.