Get the FREE Ultimate OpenClaw Setup Guide →

spring-ai -sse

MCP server from ajeetcloud/spring-ai-mcp-server-sse

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio ajeetcloud-spring-ai-mcp-server-sse java -jar spring-ai-mcp-server-sse.jar \
  --env JAVA_OPTS="additional JVM options if needed" \
  --env SPRING_PROFILES_ACTIVE="default"

How to use

This MCP server is a Spring Boot application that provides a server context for the spring-ai mcp server with Server-Sent Events (SSE) capabilities. Once the application is running, it exposes endpoints that can stream responses to clients via SSE, enabling real-time data updates and long-lived connections for interactive AI-powered workflows. Use the SSE endpoints to subscribe to live results, progress updates, or streaming sessions as part of your MCP tooling workflow.

How to install

Prerequisites:

  • Java Development Kit (JDK) 17 or newer installed on your system.
  • Optional: Maven or Gradle if you prefer building from source.

Install and run:

  1. Clone the repository or download the packaged Spring Boot jar.
  2. If building from source, use Maven or Gradle to build:
    • Maven: mvn clean package
    • Gradle: ./gradlew build
  3. Run the application:
    • If you have a jar file: java -jar spring-ai-mcp-server-sse.jar
    • If you built from source with Maven: java -jar target/<your-artifact>.jar
  4. Verify the server is running by hitting the health or info endpoint (e.g., http://localhost:8080/actuator/health).

Notes:

  • Ensure the port (default 8080) is open or configure via Spring properties if needed.
  • If you assemble a custom jar name, replace spring-ai-mcp-server-sse.jar with the actual file name.

Additional notes

Tips:

  • If you plan to expose SSE endpoints publicly, consider configuring a reverse proxy and enabling TLS.
  • Set SPRING_PROFILES_ACTIVE for different environments (dev, prod).
  • If you encounter port conflicts, change the server.port property (e.g., --server.port=8081).
  • For large streaming payloads, monitor JVM memory usage and adjust JAVA_OPTS accordingly (e.g., -Xmx2g).

Common issues:

  • Jar file not found: ensure the jar path in the command matches your build output.
  • Network/firewall blocks SSE streams: verify that long-lived connections are allowed on the chosen port.

Related MCP Servers

Sponsor this space

Reach thousands of developers