S14: MCP spike (rmcp, Claude Code and Codex as clients, VM reachability) #4

Open
opened 2026-10-02 00:16:05 +00:00 by jhgaylor · 0 comments
Owner

Blocks: #5

From PLAN.md, section "M16 → S14".


S14: spike before M16 (about half a day):

  • rmcp maturity: Streamable HTTP server, resource subscriptions, progress
    notifications, structured content, and tool annotations.
  • Claude Code as a client:
    • its MCP tool-call timeout, and whether progress notifications extend it;
    • its output-size limit (MAX_MCP_OUTPUT_TOKENS) and what truncation
      looks like;
    • whether it uses resource subscriptions at all.
  • Codex as a client: stdio and HTTP.
  • From inside a wisp VM: can a process reach an HTTP endpoint on the host
    (the bridge address, given wisp-netd's restricted set), or does the
    bridge need to run host-side?
  • Does claude-agent-acp pass mcpServers of type http as well as
    stdio?
**Blocks:** #5 _From PLAN.md, section "M16 → S14"._ --- **S14: spike before M16 (about half a day):** - `rmcp` maturity: Streamable HTTP server, resource subscriptions, progress notifications, structured content, and tool annotations. - Claude Code as a client: - its MCP tool-call timeout, and whether progress notifications extend it; - its output-size limit (`MAX_MCP_OUTPUT_TOKENS`) and what truncation looks like; - whether it uses resource subscriptions at all. - Codex as a client: stdio and HTTP. - From inside a wisp VM: can a process reach an HTTP endpoint on the host (the bridge address, given `wisp-netd`'s restricted set), or does the bridge need to run host-side? - Does `claude-agent-acp` pass `mcpServers` of type `http` as well as `stdio`?
Sign in to join this conversation.
No description provided.