Spring Boot Sample MCP Server

Created By
tobiassteidlea year ago
Overview

What is Spring Boot Sample MCP Server?

Spring Boot Sample MCP Server is a sample implementation of a Model Context Protocol (MCP) server using Spring Boot, designed for testing and debugging with the Model Context Protocol Inspector.

How to use Spring Boot Sample MCP Server?

To use the server, configure it according to the provided instructions, start the server, and integrate it with AI assistants like Claude Desktop to enable communication and data access.

Key features of Spring Boot Sample MCP Server?

  • Simple REST API for interaction
  • Integration with AI assistants via MCP
  • Unit tests included for functionality verification
  • Easy setup and configuration with Spring Boot

Use cases of Spring Boot Sample MCP Server?

  1. Testing and debugging AI model interactions.
  2. Providing real-time data access to AI assistants.
  3. Demonstrating the capabilities of the Model Context Protocol.

FAQ from Spring Boot Sample MCP Server?

  • What is MCP?

Model Context Protocol (MCP) is an open standard for AI models to communicate with external tools and data sources.

  • How do I run the server?

Follow the configuration instructions and use Maven to build and run the server.

  • Can I use this server with other AI assistants?

Yes, it can be integrated with any AI assistant that supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tobiassteidle
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