MCP.so
ログイン

MCP Tools

@michaelnugent

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

michaelnugent

MCP Tools について

A proxy server and tools manager for the Model Context Protocol (MCP) that facilitates communication between LLM applications and remote MCP-compatible services.

MCP Tools の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

MCP Tools のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is MCP Tools?

MCP Tools provides two components for working with the Model Context Protocol: a proxy that forwards stdin data to an HTTP endpoint and returns responses, and a server that loads MCP executables from a directory and exposes their tools to clients via HTTP or stdio with namespaced names.

How to use MCP Tools?

Build all components with make, then run the server (make run-server for HTTP mode, make run-server-stdio for stdio mode). Run the proxy with make run-proxy or directly via ./mcp-proxy -endpoint="https://example.com/mcp". The server scans a directory (default ./mcps) for MCP executables and automatically discovers their tools.

Key features of MCP Tools

  • Proxy forwards MCP requests from stdin to a remote HTTP endpoint
  • Server loads and manages MCP executables from a directory
  • Automatic tool discovery and namespace-based naming (mcpname.toolname)
  • Supports both HTTP and stdio transport modes
  • Compiled as a single Go executable for easy deployment
  • Includes example MCPs (hello-mcp, calculator-mcp) for testing

Use cases of MCP Tools

  • Proxy MCP communication from stdin to a remote HTTP server
  • Aggregate tools from multiple local MCP executables into one HTTP or stdio server
  • Develop and test MCP-compatible tools using the provided examples
  • Deploy a lightweight MCP server without requiring a language runtime

よくある質問

1

What is the advantage of using Go for MCP Tools?

Go compiles to a single executable file, eliminating runtime and library dependencies, reducing deployment difficulties and breaking updates.

2

What transport modes does the server support?

The server can run in HTTP mode (default on port 8080) or stdio mode (using the `-stdio` flag).

3

How are tools from different MCPs organized?

The server namespaces tools by adding the MCP executable name as a prefix, e.g., `mcpname.toolname`.

4

What is the default endpoint for the proxy?

The proxy defaults to `http://localhost:8080` and expects a JSON content type, with configurable timeout and buffer size.

5

How do I test the proxy with example tools?

After starting the server, run `make test-proxy` for a basic tools/list request, or `make test-hello` and `make test-add` to test specific tools.

コメント

「その他」の他のコンテンツ