From 7c3beab1d71bef2284c2ef2095ec33b3c0c8b2d7 Mon Sep 17 00:00:00 2001 From: haosenwang1018 Date: Sat, 18 Apr 2026 08:49:34 +0000 Subject: [PATCH] docs: clarify streamable HTTP support Signed-off-by: haosenwang1018 --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d1c6a3..73aa79d 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ A lightweight, Bun-based CLI for interacting with [MCP (Model Context Protocol)] - 📦 **Single Binary** - Compile to standalone executable via `bun build --compile` - 🔧 **Shell-Friendly** - JSON output for call, pipes with `jq`, chaining support - 🤖 **Agent-Optimized** - Designed for AI coding agents (Gemini CLI, Claude Code, etc.) -- 🔌 **Universal** - Supports both stdio and HTTP MCP servers +- 🔌 **Universal** - Supports stdio and streamable HTTP MCP servers - ⚡ **Connection Pooling** - Lazy-spawn daemon keeps connections warm (60s idle timeout) - � **Tool Filtering** - Allow/disable specific tools per server via config - 📋 **Server Instructions** - Display MCP server instructions in output @@ -478,6 +478,12 @@ MCP_DAEMON_TIMEOUT=120 mcp-cli # 2 minute idle timeout MCP_DEBUG=1 mcp-cli info # See daemon debug output ``` +### HTTP transport support + +Remote `url` configs currently use the MCP SDK's **streamable HTTP** client transport. Local stdio servers continue to work as usual, and remote MCP servers should expose a streamable HTTP endpoint. + +**Important:** `mcp-cli` does **not** currently support legacy HTTP+SSE transports. If a remote MCP server only offers SSE, it may work in other MCP clients but not in `mcp-cli` yet. + ### Connection Model (Direct) When daemon is disabled (`MCP_NO_DAEMON=1`), the CLI uses a **lazy, on-demand connection strategy**. Server connections are only established when needed and closed immediately after use.