spring-mcp-server-sample

Created By
ricken07a year ago
MCP Server Sample
Overview

what is spring-mcp-server-sample?

The spring-mcp-server-sample is a sample project demonstrating the use of the MCP (Microservices Communication Protocol) server built with Spring framework.

how to use spring-mcp-server-sample?

To use this project, clone the repository from GitHub, set up your Java environment, and run the server using the provided commands in the documentation.

key features of spring-mcp-server-sample?

  • Demonstrates the implementation of MCP server using Spring.
  • Provides sample configurations and setup instructions.
  • Easy to extend and modify for custom use cases.

use cases of spring-mcp-server-sample?

  1. Learning how to implement a microservices communication server.
  2. Extending the sample for custom microservices applications.
  3. Testing and experimenting with MCP protocols in a controlled environment.

FAQ from spring-mcp-server-sample?

  • What is MCP?

MCP stands for Microservices Communication Protocol, which facilitates communication between microservices.

  • Is this project suitable for production use?

This is a sample project intended for learning and experimentation, not recommended for production use without modifications.

  • How can I contribute to this project?

You can contribute by submitting issues or pull requests on the GitHub repository.

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