AI GitHub
mcp-proxy for adapting MCP server connections
Bridge supported local and remote MCP transports from a lightweight proxy.
Key Takeaways
- The proxy changes how a client reaches a server.
- Read the transport matrix for this repository before setting up the bridge.
- Use a local fixture to check tool listing and invocation on both sides of the proxy.
- Similar project names refer to different proxies.
How it works
The proxy changes how a client reaches a server. It enables an existing tool implementation to remain in place when a client expects a different connection mechanism.
What you need
Read the transport matrix for this repository before setting up the bridge. Keep the upstream server command or URL explicit so you can test the two connections independently.
What to try first
Use a local fixture to check tool listing and invocation on both sides of the proxy. Confirm which process owns the connection when the client reconnects.
Check how the proxy behaves when the stdio server writes diagnostics. Protocol output and logging need to remain separate for a reliable connection.
Where to look for failures
Similar project names refer to different proxies. Read the exact repository's transport options and test credential forwarding before putting it in front of private tools.
Related Franklin pages
Verify capabilities before and after adding a bridge. Then test a client disconnect so you know which process and connection remain alive.
- Inspect MCP connections and exercise tools, resources and prompts during development. MCP Inspector for testing server behavior
- Connect MCP clients and servers that speak different supported transports. Supergateway for bridging MCP transports
Browse Franklin for concrete examples of tools and services exposed through MCP. Franklin’s MCP directory
Project documentation
Try it for your workflow
Explore the project’s documentation for setup and usage, or save this page to a collection for later.
Read the project documentation ↗