Obot supports both local and remote MCP servers. For local MCP servers, they are hosted on the Obot platform and published as a remote MCP server to clients.

Obot supports any MCP hosts and clients that can connect to remote MCP servers. Obot does include an out-of-the box Chat interface but will support all of the popular MCP hosts such as Cursor, Claude Desktop, VSCode, and Cline.

Obot is built for all of these teams. IT admins use Obot to onboard, secure and manage MCP Servers. Developers access authorized MCP servers via the Obot Catalog. Business users can interact with MCP servers safely by accessing a curated list of MCP servers via the catalog and connecting them to their preferred MCP chat client, or access them via the Obot Chat interface.

Obot supports identity providers like Google and GitHub. Obot Enterprise edition includes support for Okta and Microsoft Entra.

Obot enforces strict authentication and authorization for every request, with full audit logs and policy controls. You define what MCP each user can access and Obot ensures only those requests are allowed through.

Yes Obot is open-source and free to use. You can self-host it or run it in your own cloud environment. If you need support, or features like Okta or Entra support, we offer Obot Enterprise Edition.

You can launch a pilot in minutes by deploying Obot on any Kubernetes cluster. Out of the box, Obot includes a curated set of common MCP servers that we maintain. Once you have Obot running, you can add in your internal MCP servers, configure access control and security policies, and then publish your MCP catalog to internal employees.