MCP Mediator – Automatic MCP Server Generation

Created By
makbna year ago
Automatically generate an MCP Server from existing source code, service classes, helper methods, and external MCP tools. The MCP Mediator aggregates various sources and tools into a unified system, enabling seamless automatic generation of a complete MCP Server.
Overview

What is MCP Mediator?

MCP Mediator is a Java-based implementation of the Model Context Protocol (MCP) mediator, designed to facilitate seamless integration between MCP clients and servers, enabling efficient communication and tool execution in the MCP ecosystem.

How to use MCP Mediator?

To use MCP Mediator, ensure you have Java 17 or later and Maven 3.6 or later installed. You can integrate it with Spring Boot for automatic configuration of the MCP server for available endpoints.

Key features of MCP Mediator?

  • Support for stdio transport
  • Extensible request handling system
  • Integration with Spring Framework and Spring Boot (WIP)
  • Comprehensive error handling (WIP)
  • Configurable server capabilities
  • Support for multiple tool implementations

Use cases of MCP Mediator?

  1. Facilitating communication between different MCP clients and servers.
  2. Managing tool execution in a distributed environment.
  3. Integrating various services like Docker and Dropbox into the MCP ecosystem.

FAQ from MCP Mediator?

  • What are the prerequisites for using MCP Mediator?

You need Java 17 or later, Maven 3.6 or later, and Spring Boot 3.2.2 or later for Spring Boot integration.

  • Is MCP Mediator open for contributions?

Yes! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
makbn
Star
2
Language
Java
License
GPL-3.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