MCP Net

This project provides a set of tools for handling the Model Context Protocol (MCP), including proxy and server tools, supporting communication with MCP-compatible services via HTTP or standard input/output.

Developer tools Artificial intelligence chatbots #Protocol proxy #Tool management #Model service #HTTP communication .Go

rating : 2.5 points

downloads : 5.1K

update time : 2025-04-28

Open Site

What are MCP Tools?

MCP Tools provides a complete solution for managing and using tools that comply with the Model Context Protocol. It consists of two main components: the MCP Proxy for forwarding requests and the MCP Server for managing and executing MCP tools.

How to use MCP Tools?

Users can interact with MCP tools through a simple command-line interface. The MCP Proxy forwards user input to the specified endpoint, while the MCP Server is responsible for loading and executing various MCP tools.

Applicable scenarios

Suitable for scenarios where multiple command-line tools need to be centrally managed and invoked, especially when these tools need to be deployed across platforms or run on remote servers.

Main features

Request forwarding

The MCP Proxy can forward local requests to any HTTP endpoint, simplifying the invocation of remote tools.

Tool management

The MCP Server can automatically discover and load MCP tools in the directory without complex configuration.

Multi-mode support

Supports two communication modes: HTTP and standard input/output, adapting to different usage scenarios.

Advantages

Deployed as a single executable file without a complex runtime environment

Automatic tool discovery mechanism simplifies management

Supports cross-platform use

Lightweight design with low resource consumption

Limitations

Currently only supports tools developed in Go language

Limited isolation between tools

Lack of graphical user interface

How to use

Install MCP components

Download or compile the executable files of the MCP Proxy and Server.

Configure the MCP tool directory

Place the developed MCP tool executable files in the specified directory.

Start the MCP Server

Run the server and specify the tool directory and listening port.

Use tools through the proxy

Use the MCP Proxy to connect to the server and invoke tools.

Usage examples

Invoke the greeting tool

Use the hello-mcp tool to generate a greeting message.

Use the calculator tool

Invoke the calculator-mcp for addition operations.

Frequently Asked Questions

What programming language should be used to develop MCP tools?

How to view the list of available tools?

Can multiple MCP Servers be run simultaneously?

Related resources

Go official website

Official website of the Go programming language

MCP protocol specification

Technical specification document of the Model Context Protocol

Example code repository

Example code for MCP tool development

🚀 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: