spring-devtools
MCP server from jamesward/spring-devtools-mcp-server
claude mcp add --transport stdio jamesward-spring-devtools-mcp-server uvx mcp-proxy http://localhost:9999/sse
How to use
This MCP server integrates with a running Spring application that exposes its DevTools information via Server-Sent Events (SSE) at the /sse endpoint. The server itself is not a standalone process; you run your Spring app with DevTools enabled and point your MCP consumer to the SSE stream. As shown in the README, you can also use uvx with the mcp-proxy to connect through the SSE endpoint (http://localhost:9999/sse) if your environment expects a proxy-based MCP connection. Once connected, an AI assistant can query the running application’s DevTools information to assist with debugging, reload events, and Spring DevTools related insights. If your tooling supports SSE MCP servers, point it directly at http://localhost:9999/sse; otherwise, use uvx mcp-proxy http://localhost:9999/sse to bridge to the MCP server.
How to install
Prerequisites:
- Java (JDK) installed
- Gradle installed or use the Gradle wrapper in your project
Installation steps:
-
Add the MCP server dependency to your Spring project (Gradle):
developmentOnly("com.jamesward:spring-devtools-mcp-server:0.0.3")
-
Build and run your Spring application as you normally would. Ensure DevTools is enabled and the SSE endpoint is available at http://localhost:9999/sse.
-
If you are using a proxy-based MCP setup, you can connect via uvx:
uvx mcp-proxy http://localhost:9999/sse
-
When the app is running, configure your MCP client to connect to the SSE endpoint (http://localhost:9999/sse) or through the uvx proxy as shown above.
Additional notes
- The port is listed as 9999 by default in the README; you may want to configure a different port in your Spring application if needed (see TODO: Configurable port).
- Logging and additional telemetry can be added in future iterations (see TODO: Logging).
- If you cannot connect directly to SSE, use the uvx mcp-proxy approach described in the README.
- Ensure your environment variables for Gradle publishing (if releasing locally) are set as shown in the Release steps, but they are not required for running the MCP server itself.
