Skip to content

Add existing MCP client bridge - #511

Merged
imran-siddique merged 1 commit into
mainfrom
agent/existing-mcp-client-bridge
Aug 14, 2026
Merged

Add existing MCP client bridge#511
imran-siddique merged 1 commit into
mainfrom
agent/existing-mcp-client-bridge

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

Closes #491. Closes #510.

Adds a stdio bridge that existing MCP clients can launch from their standard mcpServers configuration. Tokens are read from an environment variable, stdout remains strict JSON-RPC, failures are fail closed, and the tutorial states plainly that the local bridge is outside the attested boundary and is removable by the user.

Evidence:

  • design issue design: stdio client bridge for existing MCP clients #510 existed before implementation
  • official MCP Python client launched the bridge as a subprocess
  • client initialized, listed tools, and called a tool through a real cMCP HTTP server
  • the real cMCP audit chain contained the tool call
  • focused bridge tests: 5 passed
  • full suite: 1161 passed, 24 skipped
  • Ruff, mypy, Bandit, and git diff check passed

@imran-siddique
imran-siddique marked this pull request as ready for review August 14, 2026 22:37
@imran-siddique
imran-siddique merged commit d083cdf into main Aug 14, 2026
13 checks passed
@imran-siddique
imran-siddique deleted the agent/existing-mcp-client-bridge branch August 14, 2026 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

design: stdio client bridge for existing MCP clients adoption: no path for a real MCP client to sit behind the gateway

1 participant