obot-platform / obot

What it does

• Expose MCP servers through virtual MCP servers (vMCPs), which combine one or more catalog servers behind a single endpoint, whether those servers are hosted by Obot or run outside it.
• Reach remote MCP servers on private networks through MCP tunnels, which connect outbound to Obot so no inbound port has to be opened.
• Pin each vMCP component to a snapshot of its catalog entry, so catalog changes take effect only through an explicit upgrade.
• Control server and tool access by user or identity-provider group through vMCP profiles.
• Enable tool search on large vMCPs so clients search for and call tools without loading every tool definition into the model's context.