java-sdk-mcp-server

Created By
moises-paschoalicka year ago
This project uses only the Java SDK MCP library. For the Spring-based implementation, please refer to the spring-ai-mcp-server repository.
Overview

what is java-sdk-mcp-server?

java-sdk-mcp-server is a project that utilizes the Java SDK MCP library to provide a server implementation. It is designed for developers looking to integrate MCP functionalities using Java.

how to use java-sdk-mcp-server?

To use java-sdk-mcp-server, clone the repository from GitHub and follow the setup instructions in the README file to configure the server for your application.

key features of java-sdk-mcp-server?

  • Utilizes the Java SDK MCP library for server functionalities.
  • Provides a straightforward implementation for Java developers.
  • Easy integration with existing Java applications.

use cases of java-sdk-mcp-server?

  1. Building Java applications that require MCP functionalities.
  2. Integrating with other Java-based services.
  3. Developing server-side applications using the Java SDK MCP library.

FAQ from java-sdk-mcp-server?

  • Is this project suitable for production use?

The project is in its early stages and may require further testing before being used in production environments.

  • Where can I find the documentation?

Documentation can be found in the repository's README file on GitHub.

  • Can I contribute to this project?

Yes! Contributions are welcome, and you can submit pull requests on GitHub.

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