Mcproxy

🚀 MCProxy

MCProxy exposes resources, prompts, and tools from connected MCP servers to clients, with options to rename identifiers.

🚀 Quick Start

By default, MCProxy exposes resources, prompts, and tools from all connected MCP servers to clients using the same identifiers (names, URIs, etc.). These identifiers can be renamed (see the Features section below).

📚 Documentation

Configuration

To connect to MCP servers, MCProxy uses the same configuration file format as defined in the MCP documentation. Additionally, there are some internal configurations for MCProxy itself. Finally, each module can also provide some configuration instructions. Here are some examples:

Features

Here are some examples of features that can be achieved either through MCProxy itself or via external modules:

Logging

MCProxy can log all messages exchanged between the client and MCP servers.

Configuration

• What to log
• Where to log

Capability Aggregation

MCProxy can aggregate capabilities from different MCP servers into meaningful packages.

Capability Blocking

MCProxy may expose only a subset of the capabilities provided by MCP servers.

Configuration

• List of capabilities to block

Capability Conflict Resolution

As the number of MCP servers grows rapidly, identifier conflicts may occur. MCProxy can rename capabilities to make them unique from the client's perspective and handle routing messages to the appropriate MCP servers.

Configuration

• List of mappings from server/identifier => new identifier

Content Update

Text content can be filtered or enriched when transmitted through MCProxy.

Instant Translation (i18n)

The current version of the MCP specification does not support i18n (see my related issue).

MCProxy can perform translations on the fly using translation APIs or LLMs.

Configuration

• Preferred languages
• Connection parameters to the translation tool

External Modules

They provide additional functionality to MCProxy beyond its basic features.

They exist as independent projects and can be directly plugged into MCProxy.

A list of such modules can be maintained, similar to the current lists of MCP clients/servers (e.g., here, here, or here).

Hosting

They can be hosted locally or remotely as a service.

Functionality

They declare their own "functionality", i.e., the types of MCP messages they are interested in. They are called in the order declared in the configuration file.

Protocol

The protocol between MCProxy and external modules strongly borrows from the MCP specification, but the workflow is different: typically, the message type of the response is the same as the message sent.

For example:

• A GetPromptRequest message sent to a module will return an updated GetPromptRequest message.
• A ListToolsResult message sent to a module will return an updated ListToolsResult message.

(TBD: Specification of such a protocol)