fix: mcp stdio transport crashes with unexpected 'host' keyword argument

[Heliopause0916]

Fixes Bug 2 from #115 — stdio transport crashes with TypeError: TransportMixin.run_stdio_async() got an unexpected keyword argument 'host'

This is a follow-up fix to PR #116, which addressed the empty Authorization header issue but left the stdio transport crash unresolved.

Problem

When running open-terminal mcp --transport stdio, the command crashes with:

TypeError: TransportMixin.run_stdio_async() got an unexpected keyword argument 'host'

Root cause: The mcp_server.run() call unconditionally passes host and port arguments regardless of the transport type. FastMCP's stdio transport does not accept these parameters.

# Before: Always passes host/port
mcp_server.run(transport=transport, host=host, port=port)

Solution

Conditionally pass host and port only for non-stdio transports:

# Only resolve host/port for non-stdio transport modes
if transport != "stdio":
    host = host or cfg.get("host", "0.0.0.0")
    port = port if port is not None else cfg.get("port", 8000)

# ... (API key resolution logic) ...

# Conditionally call run() with appropriate parameters
if transport == "stdio":
    mcp_server.run(transport="stdio")
else:
    mcp_server.run(transport=transport, host=host, port=port)

Testing

Verified on Windows:

# stdio transport - now works correctly
open-terminal mcp --transport stdio --api-key test123

# streamable-http transport - still works as expected  
open-terminal mcp --transport streamable-http --host 0.0.0.0 --port 9000 --api-key test123

Related

• Fixes open-terminal mcp always sends empty Authorization header, causing 401 on all tool calls — plus stdio transport crashes with unexpected host kwarg #115 (Bug 2 - stdio transport crash)
• Builds on fix: mcp command always sends empty Authorization header, causing 401 on all tool calls #116 which fixed Bug 1 (empty Authorization header)