spring-api-intel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPRING_BOOT_URL | No | Base URL of a running app for live Swagger/Actuator enrichment e.g. http://localhost:8080 | |
| SPRING_PROJECT_ROOT | No | Pre-set a project path at startup. Leave empty — server remembers last project via state file |
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
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_endpointsA | List all REST endpoints in the Spring Boot project. Enriches with live Swagger/Actuator data if the app is running. |
| trace_endpointA | Trace the full call chain for an endpoint path. Shows controller → service → repository. |
| clone_and_set_projectA | Clone a public GitHub repository and index it as the active project. Accepts a full URL (https://github.com/owner/repo) or shorthand (owner/repo). Uses --depth=1 for speed. Re-uses existing clones automatically. |
| list_cloned_reposA | List all GitHub repos currently cached in the temp folder with their disk usage. |
| delete_cloned_repoB | Delete a specific cloned repo from the temp folder to free up disk space. |
| delete_all_cloned_reposA | Delete all cloned repos from the temp folder to free up disk space. |
| generate_dashboardA | Generate a visual HTML architecture dashboard — layers, dependency graph, tech stack, and class overview. Opens in any browser. |
| find_usagesB | Find all classes in the codebase that reference a given class name. |
| summarize_classB | Get a structured summary of a Java class including its annotations, dependencies, and methods. |
| reindexA | Re-scan the project directory to pick up new or changed files. |
| get_project_infoA | Extract project metadata from pom.xml or build.gradle — Java version, Spring Boot version, build tool, and all dependencies. |
| set_projectB | Switch the active Spring Boot project by providing a directory path. Use this to point the server at a different codebase. |
| clear_saved_stateA | Clear the saved project state so the server starts fresh next session. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize-class | Get an AI summary of a Java class in your Spring Boot project |
| generate-dashboard | Generate a visual HTML architecture dashboard for the current project |
| trace-endpoint | Trace an endpoint through controller → service → repository |
| onboarding-overview | Full codebase overview for a new developer joining the project |
| find-usages | Find all classes that reference a given class |
| architecture-review | Full architecture review — endpoints, dependencies, design observations |
| analyse-github-repo | Clone and analyse any public Spring Boot GitHub repository |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no overlap. For example, clone_and_set_project and set_project differ in operation (clone vs just set), delete_all_cloned_repos vs delete_cloned_repo differ in scope. All other tools target unique actions.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., clear_saved_state, clone_and_set_project, list_endpoints, trace_endpoint). No mixing of styles or vague verbs.
13 tools is well-scoped for a Spring Boot analysis server. It covers project setup, information retrieval, endpoint analysis, code search, and maintenance without being bloated.
Core workflows are covered: project selection, metadata extraction, endpoint tracing, class summaries, usage search, and dashboard generation. A minor gap is the lack of a tool listing all classes or packages, though the dashboard may compensate.