MCP Client SSE

Created By
Shaamama year ago
Spike Project on building MCP Clients to connect with MCP Servers to access the tools exposed by the servers
Overview

what is MCP Client SSE?

MCP Client SSE is a Spring Boot-based Java application designed to connect with MCP Servers, allowing users to access various tools exposed by these servers.

how to use MCP Client SSE?

To use MCP Client SSE, clone the repository, build the project using Gradle, and run the application. Configuration is done through the application.properties file.

key features of MCP Client SSE?

  • Synchronous integration with MCP servers.
  • Configurable tool callback provider.
  • Integration with OpenAI API for enhanced functionality.
  • Customizable application properties for user-specific configurations.

use cases of MCP Client SSE?

  1. Connecting to MCP servers for tool access.
  2. Integrating AI functionalities via OpenAI API.
  3. Customizing client properties for specific server interactions.

FAQ from MCP Client SSE?

  • What is the primary purpose of MCP Client SSE?

It serves as a client to connect and interact with MCP servers, facilitating tool access and integration.

  • Is there a specific programming language required to use MCP Client SSE?

Yes, it is built using Java and requires knowledge of Spring Boot for configuration and usage.

  • How can I configure the application?

Configuration is done through the application.properties file, where you can set various parameters for the client.

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