Skip to main content
Glama
Sign In
spring-runtime-mcp

spring-runtime-mcp

by neilmorse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to spring-runtime-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Runtime Proof

      fantasyce
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes three read-only tools that list local Agent and MCP runtime candidates, inspect running processes, and check a live runtime against an approved artifact expectation. Returns explicit verdicts such as matched, stale, leaked, conflict, unknown, or not running without exposing argv, environment values, or file contents.
      1
      Apache 2.0

    • DevTwin MCP

      JaydeepDhamecha
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding agents with structured, evidence-based diagnostics about the local development environment, detecting tech stack, runtime mismatches, dependency state, services, ports, and Git status without exposing secrets or using network calls.
      10
      Apache 2.0

    • hono

      Rixmerz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only semantic analysis of 4.x route-based projects: composed mounted paths, middleware execution order, validators, RPC types, request tracing, change-impact analysis and 36 lint rules, plus a headless CLI for CI quality gates. Tooling stays project-local with no installed dependencies, so agents can query a route table, diagnose 404s and gate changes without touching the codebase.
      MIT

    • ansible-mcp

      YawLabs
      A
      license
      A
      quality
      A
      maintenance
      Read-only server that reports what is actually true in a local Ansible checkout: the option specs of installed modules, task-argument validity checks, role interfaces, redacted inventory, play structure, effective config, requirements drift, and which tasks a collection upgrade would break. It lets coding agents verify specs and arguments against the installed collections before writing anything, without running plays, connecting to managed hosts, or supplying vault secrets.
      11
      92 npm
      1
      MIT

    • codebase-doctor

      subhajitlucky
      A
      license
      A
      quality
      A
      maintenance
      Evidence-backed, read-only codebase diagnostics for coding agents: secrets, dependency, RLS, and source-impact audits with a verify loop and PR review verdicts. Never writes files or uses the network by default.
      7
      114 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources