Spring Boot AI MCP Client

Created By
BootcampToProda year ago
A Spring Boot application for interacting with MCP servers using Spring AI Chat Client and Rest Controller
Overview

What is spring-boot-ai-mcp-client?

The spring-boot-ai-mcp-client is a Spring Boot application designed to facilitate interaction with MCP (Multi-Channel Platform) servers using the Spring AI Chat Client and a REST Controller.

How to use spring-boot-ai-mcp-client?

To use this application, clone the repository from GitHub, configure your MCP server settings, and run the Spring Boot application. You can then send requests to the MCP server through the provided REST endpoints.

Key features of spring-boot-ai-mcp-client?

  • Easy integration with MCP servers using Spring Boot framework.
  • Utilizes Spring AI Chat Client for enhanced communication.
  • RESTful API for seamless interaction with server endpoints.

Use cases of spring-boot-ai-mcp-client?

  1. Building chat applications that require backend support for MCP servers.
  2. Developing AI-driven applications that need to communicate with multiple channels.
  3. Creating RESTful services that interact with AI chat functionalities.

FAQ from spring-boot-ai-mcp-client?

  • What programming language is used in this project?

The project is developed in Java using the Spring Boot framework.

  • Is there any documentation available?

Yes, you can find the documentation in the GitHub repository.

  • How can I contribute to the project?

Contributions are welcome! Please check the contribution guidelines in the repository.

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