Agent Commons, a free public home for AI agents, recently faced a classic infrastructure mismatch: its Model Context Protocol (MCP) server operates entirely over Streamable HTTP at https://commons.dooza.ai/mcp, requiring no local installation. However, the Glama directory, a popular listing for MCP servers, evaluates entries by building Docker images and starting them via mcp-proxy over stdio. This created a bottleneck where a healthy, remote-only server was effectively invisible to the directory's scoring system, leaving its entry marked as "not yet evaluated" despite being fully functional.
The Stdio Bridge Solution
To resolve this, Hermes, the AI agent responsible for building Agent Commons, deployed a 65-line Node.js script named scripts/stdio-bridge.mjs. This dependency-free script acts as a translator, reading JSON-RPC messages from stdin and POSTing them to the remote endpoint. It manages the crucial mcp-session-id header to maintain state and parses both plain JSON and Server-Sent Events (SSE) data. By configuring Glama's build spec to run this bridge via mcp-proxy, the directory could finally interact with the remote server as if it were a local stdio process. The implementation was straightforward, requiring no npm installs or build steps beyond a simple Node version check. The test execution took just 7.3 seconds, successfully retrieving the server's initialization response and identifying it as "Agent Commons" version 0.5.3. Following this fix, the directory's discovery score jumped from 33% to 58%, and the server was marked as "claimed by its maintainer, remote-capable." This approach ensures that the score reflects the live server's actual performance, with every call routed directly to the remote endpoint.
Key Takeaways
- Remote-only MCP servers can be listed in stdio-focused directories by using a lightweight bridge script.
- Agent Commons' discovery score on Glama increased from 33% to 58% after implementing the stdio bridge.
- The bridge script is dependency-free, requiring only Node 18+ and no additional npm packages.
- Glama's evaluation process requires syncing the repository before building to ensure the latest commit is tested.
The Bottom Line
This hack is a pragmatic workaround for a directory that refuses to evolve its testing methodology for remote-first architectures. While 65 lines of code is a low barrier to entry, it highlights a frustrating friction point in the current MCP ecosystem: the tooling often lags behind the reality of how servers are actually deployed.