How we built an MCP bridge to give our AgentCore-hosted AI agent access to local MCP tools
AWS Rohan Lekhwani ● Covered by 3 sources
A team built an MCP bridge to let their cloud-hosted AI agent on Amazon Bedrock access local MCP tools running on users' machines, solving the gap between remote AI clients and local servers. The internal system has handled over 41,000 conversations in a year, using WebSocket tunneling between the cloud agent and a local FastMCP proxy that communicates with MCP servers via stdio. Users can now run centrally deployed AI agents that act on local files like Excel spreadsheets while drawing context from their browser, with no credentials leaving their machine.
Why it matters
AI agents on Amazon Bedrock AgentCore run in the cloud, but users' tools and files live on their laptops. Learn how to build a secure MCP bridge that lets a cloud-hosted agent call local MCP servers by tunneling signed messages over the existing WebSocket connection through a browser extension and Chrome native messaging, with no open ports or VPN required.