Spring MCP Server Demo

Created By
esurovtseva year ago
Remote MCP (Model Context Protocol) server built with Spring Boot and SSE. Demonstrates how to register tools, configure endpoints, and stream results to connected LLM clients using the Spring AI MCP SDK.
Overview

What is Spring MCP Server Demo?

Spring MCP Server Demo is a demonstration project that showcases how to build a remote Model Context Protocol (MCP) server using Spring Boot and Server-Sent Events (SSE). It allows for the registration of tools and streaming of results to connected LLM clients using the Spring AI MCP SDK.

How to use Spring MCP Server Demo?

To use the Spring MCP Server Demo, you can run it using Maven or build it into a JAR file. The server will start at http://localhost:8080, and you can test it using the MCP Inspector tool.

Key features of Spring MCP Server Demo?

  • Complete MCP server implementation using Spring AI
  • Tool registration and callback handling
  • RAG search service as a practical example tool
  • Docker support for easy deployment

Use cases of Spring MCP Server Demo?

  1. Building AI applications that require tool integration through the MCP protocol.
  2. Testing and demonstrating the capabilities of the MCP server with various tools.
  3. Enhancing AI models by providing access to specific information sources through registered tools.

FAQ from Spring MCP Server Demo?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows AI models to discover and use tools provided by a server.

  • How can I test my MCP server?

You can use the MCP Inspector tool to test your server without needing to integrate with an LLM.

  • Is Docker support available?

Yes! The project includes Docker support for easy deployment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
esurovtsev
Star
0
Language
Java
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago