Get started

Introducing the Obot MCP Gateway

Manage, Secure, and Scale MCP Adoption Across Your Organization

Deploy Obot Explore the Catalog Request a Demo

WHAT IS obot?

Obot MCP Gateway is an open source platform that helps IT teams bring order to the rapid growth of MCP servers—so developers and employees can securely connect AI tools to the apps and data they need.

Obot on Github

Secure MCP Management Unlocks Enterprise AI

MCP servers enable AI tools and agents to connect with internal systems — but discovery, documentation, security, and governance are often fragmented and chaotic.

  • Onboard and manage MCP servers
  • Define secure access policies
  • Track usage, performance, and compliance
  • Help users find and connect to trusted MCPs

Obot: A complete platform for MCP

Central Control Plane for IT

Define access control policies, onboard new MCPs, track usage, and troubleshoot—all from a modern UI or GitOps flow.
Universal MCP Hosting & Proxying

Support local, remote, and multi-tenant MCPs. Host your own when needed, and route everything securely through Obot.
Automated Documentation & Discovery

Give users a searchable directory of available MCPs—complete with live documentation, capabilities, and IT-verified trust levels.
Instant MCP Connections

Users generate URLs to connect MCPs to their favorite AI clients, or interact with them directly via Obot’s chat client.

How Obot Works

Obot MCP Gateway gives IT a complete control plane for securely managing MCP servers, while providing users a seamless way to discover and connect to them.

01

Admin Setup & Integration

IT teams deploy the Obot Gateway Server and connect it to their organization’s identity provider—such as GitHub, Google, Okta, or Microsoft Entra. This establishes secure, authenticated access for all users.

02

Catalog Configuration

Out of the box, Obot includes a library of popular MCP servers (e.g., Outlook, Slack, Notion, GitHub). IT can add additional internal or third-party MCPs via the UI or through GitOps workflows.

03

Access Control & Policy Management

Admins define which users and teams can access which MCPs, using fine-grained access policies. These policies ensure only authorized employees can discover and connect to approved services.

04

User Discovery & Connection

Once published, users log in to browse their personalized MCP catalog. Each listing includes descriptions, capabilities, and usage guidance. When a user selects an MCP, Obot generates a unique connection URL that can be used with AI clients (e.g., Claude, Cursor, VSCode, enterprise chat tools, or custom agents).

05

Intelligent Routing & Hosting

If it’s a remote third-party MCP (e.g., from Zapier or AWS) Obot proxies all traffic, enforcing policies and logging access. If it’s a hosted MCP, Obot automatically deploys the server in a container on the organization’s Kubernetes cluster, running it securely on-demand.

06

Full Visibility & Control

All interactions are routed through Obot’s secure proxy layer, allowing IT to monitor usage, audit access, troubleshoot issues, and manage updates from a centralized control plane.

Why Now?

MCPs are becoming the backbone of AI integration. Without a control layer, organizations risk shadow infrastructure, data leaks, and lost productivity. Obot helps you accelerate adoption and stay in control—before the chaos spreads.

Schedule a Demo

Get started

Ready to scale your MCP
infrastructure without losing
control?

Get Started Explore the Docs Join the Community

FAQ

Product FAQs

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.

Latest News

Home

AI Agents are systems that can independently accomplish tasks on a user’s behalf with a high degree of autonomy.

Read More

Home

There are more and more MCP servers coming out every day, and the list is becoming long. There are a lot of good MCP servers, and a lot of MCP servers that might be useless to you.

Read More

Home

MCP or Model Context Protocol is a relatively new concept in the world of AI, but what is it and how can it help you?

Read More

Read More