What I've started experimenting with and will continue to explore is to have project-specific MCP tools. I add MCP tools to tighten the feedback loop. I want my Agent to be able to act autonomously but with a tight set of capabilities that don't often align with off-the-shelf tools. I don't want to YOLO but I also don't want to babysit it for non-value-added, risk-free prompts. So, when I'm developing in go, I create…
Horizontal scaling of remote MCP Servers is something the spec is sadly lacking any recognition around. If you've done work in this space, bravo. I've been using a message bus to decouple the HTTP servers from the MCP request handlers. I'm still evolving the solution, but it's been interesting so far.
It goes a tad beyond the spec minimum because I think it's valuable to be able to persist some small KV data with sessions and users.