MCP.so
ログイン

MCP Transport Prototype

@Amishk599

基本情報

カテゴリ

その他

ライセンス

MIT

トランスポート

stdio

作者

Amishk599

MCP Transport Prototype について

A prototype implementation to build custom MCP server that is accessible over stdio and SSE transport

#mcp#transport#prototype

MCP Transport Prototype の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-transport-prototype": {
      "command": "python",
      "args": [
        "main.py",
        "--transport",
        "sse"
      ]
    }
  }
}

MCP Transport Prototype のツール

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

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

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

概要

What is mcp-transport-prototype?

mcp-transport-prototype is a prototype implementation for understanding how to build a custom MCP server accessible over both stdio and SSE transports. It explores the differences between Server-Sent Events (SSE) and standard input/output (stdio) for MCP communication.

How to use mcp-transport-prototype?

Run the server with uv run main.py in one terminal, and the client with uv run mcp_client.py in another to test the SSE transport. No further configuration details are provided.

Key features of mcp-transport-prototype

  • Implements MCP server over SSE and stdio transports
  • Demonstrates one-way real-time streaming via SSE over HTTP
  • Shows traditional process communication via stdio
  • Includes a sample client script to test SSE mode

Use cases of mcp-transport-prototype

  • Understanding how to build custom MCP servers with different transports
  • Testing SSE for web dashboards or browser-based apps needing live updates
  • Using stdio for command-line tools or LLM agents launching MCP as subprocess

よくある質問

1

What is the difference between SSE and stdio transports?

SSE runs the MCP server as a separate HTTP service, pushing real-time updates one-way from server to client over the network. Stdio launches the server as a subprocess communicating via stdin/stdout, ideal for in-process tools without network overhead.

2

What runtime dependencies are required?

The prototype uses `uv` for running Python scripts. No additional dependencies are listed.

3

How do I test the SSE transport?

Run `uv run main.py` in one terminal and `uv run mcp_client.py` in another. The client script is available at the provided GitHub link.

4

Where does the data live?

The README does not specify data storage; it focuses on transport implementation only.

5

What are the known limitations?

SSE is one-way (server to client), unlike WebSockets. No other limitations are mentioned.

コメント

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