MCP Net

🚀 MCP Tools

This repository contains tools for handling the Model Context Protocol (MCP).

🚀 Quick Start

The MCP tools in this repository mainly include an MCP proxy and an MCP server. The proxy forwards requests to an HTTP endpoint, while the server loads and manages MCP executables from a directory and exposes them to clients via HTTP or standard input/output.

✨ Features

MCP Proxy

• Request Forwarding: It forwards data read from standard input to the specified HTTP endpoint and outputs the response to standard output.
• Simple Proxy: Implements a simple proxy for communicating with remote compatible servers.
• Go Language Advantage: Compiled into a single executable file, reducing deployment difficulties and runtime issues.

MCP Server

• Executable Loading: Loads MCP executables from a directory and provides them to clients via HTTP or standard input/output.
• Tool Listing: Returns all available tools provided by the loaded MCPs, separated by MCP namespaces.
• Dual Modes: Can run in HTTP mode or standard input mode.

Makefile Support

• Simplified Build: The included Makefile simplifies the process of building and running components.
• Component - Specific Build: Allows building specific components such as the proxy, server, or examples.

📦 Installation

This project can be built using the Makefile. Here are the build commands:

Build All Components

make

Build Specific Components

make build - proxy    # Build only the proxy
make build - server   # Build only the server
make build - examples # Build only the example MCPs

💻 Usage Examples

MCP Proxy

Basic Usage

./mcp - proxy [options]

Options

• -endpoint: Address of the HTTP endpoint to proxy (default: "http://localhost:8080").
• -content - type: Content - type header for the HTTP request (default: "application/json").
• -timeout: HTTP request timeout in seconds (default: 30).
• -buffer: Buffer size in KB for reading from standard input (default: 64).

Example

./mcp - proxy - endpoint="https://api.example.com/mcp" - content - type="application/json"

MCP Server

Basic Usage

./mcp - server [options]

Options

• -mcp - dir: Directory containing MCP executables (default: "./mcps").
• -http: Address of the HTTP server (default: ":8080").
• -name: Name of the MCP server (default: "MCP Server").
• -version: Version of the MCP server (default: "1.0.0").
• -stdio: Use standard input/output mode (default: false).

Using Makefile to Run

Start the MCP Server in HTTP Mode

make run - server

Start the MCP Server in Standard Input/Output Mode

make run - server - stdio

Connect to the Local MCP Server via the Proxy

make run - proxy

Build All Components and Run the Server and Proxy

make build && make run

🔧 Technical Details

Why Use Go for the MCP Proxy?

The code of the MCP proxy runs on the client side. Many languages require the correct runtime environment and libraries to be installed. Go compiles into a single executable file, which reduces deployment difficulties, user support requests, and issues related to runtime or version updates. Instead, it provides an HTTP endpoint.

MCP Server Directory Structure

The server expects a directory containing executable files. Each executable file must implement the MCP protocol using standard input/output. The server will:

1. Scan the executable files in the directory.
2. Run each executable file to discover the tools it provides.
3. Provide these tools to clients with namespace names (mcpname.toolname).

📄 License

This project is licensed under the MIT License.