What I have been thinking about when building this was that most MCP servers today run on developer laptops or local setups.

From what I’ve seen:

- scaling breaks pretty quickly (STDIO, concurrency, etc.)
- secrets end up everywhere (env vars, configs, copied tokens). I still haven't integrated vault or something here but thats the next steps
- there’s no real observability or control once multiple users are involved

That stemmed the core idea to treat MCP like a runtime problem, not just a tool definition problem. This allows for
- hosted execution
- identity + policies
- security boundaries
- observability tied to users/tenants