spring-boot-mcp-server-hello-world

Created By
jabrenaa year ago
Hello World MCP Server
Overview

what is spring-boot-mcp-server-hello-world?

This project is a simple Hello World server built using Spring Boot, designed to demonstrate the basic setup and functionality of a microservices architecture.

how to use spring-boot-mcp-server-hello-world?

To use this project, clone the repository from GitHub, build the application using Maven or Gradle, and run the server. You can then access the Hello World endpoint via your web browser or API client.

key features of spring-boot-mcp-server-hello-world?

  • Simple Hello World endpoint to demonstrate server functionality.
  • Built using Spring Boot for easy setup and configuration.
  • Lightweight and easy to extend for further development.

use cases of spring-boot-mcp-server-hello-world?

  1. Learning the basics of Spring Boot and microservices.
  2. Serving as a template for building more complex microservices.
  3. Demonstrating RESTful API principles.

FAQ from spring-boot-mcp-server-hello-world?

  • What is Spring Boot?

Spring Boot is a framework that simplifies the setup and development of new Spring applications.

  • How do I run the server?

After cloning the repository, use Maven or Gradle to build the project and run the application.

  • Is this project suitable for production use?

This project is intended for educational purposes and as a starting point for further development.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jabrena
Star
0
Language
-
License
Apache-2.0 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