Visit our GitHub page to download the current version of Obot & get started.
We’re excited to announce the release of Obot v0.14, which brings MCP Registry Support to the platform. This release empowers organizations to control exactly which MCP servers their users can see and install—across VS Code, GitHub Copilot, and any MCP-registry enabled client.
With version v0.14, your Obot instance can act as your organization’s MCP registry, giving you a single source of truth for MCP server visibility, access, and governance.
Watch the full walkthrough by Craig Jellick, VP of Engineering at Obot AI:
What MCP Registry Support Enables
GitHub recently introduced support for custom MCP registry URLs at the organization level. Until now, developers using VS Code or Copilot were limited to GitHub’s global MCP registry.
With Obot v0.14:
- Obot becomes your organization-wide MCP registry.
- VS Code pulls server listings directly from your Obot instance.
- You choose which servers appear to developers.
- Server installation flows through Obot’s authentication and access-control checks.
This gives engineering leaders deterministic, policy-driven control over how MCP servers are discovered and deployed across their teams.
How to Configure MCP Registry Support
Within your GitHub organization settings, navigate to:
Settings → Copilot → Policies → MCP
There you’ll find:
- Enable MCP servers in Copilot
- MCP Registry URL — point this to your Obot registry
- Restrict MCP access — choose between:
- Registry only (recommended for governance)
- Allow all
When the MCP Registry URL is blank, developers see GitHub’s global list.
Once you set it to your Obot instance, they see only the servers you authorize.
What Developers See in VS Code
Our demo shows exactly how this works in practice:
Browsing servers – When developers run “Browse MCP Servers” in VS Code:
- The list now comes from Obot, not GitHub.
- Only approved servers are shown.
- Each install triggers Obot’s authentication workflow.
Installing servers -When a developer chooses a server:
- Obot verifies they are authorized to install it.
- Installations succeed only if access rules permit.
Real-time updates – When Admins change their registry configuration in Obot:
- VS Code reflects the new list of available servers.
Controlling Visibility with Obot Access Rules
Inside Obot, administrators can configure exactly what appears in the registry:
- Start with the built-in “Allow all users” rule.
- Narrow visibility down to specific servers (e.g., Azure, BrowserBase, Calendar).
- VS Code immediately reflects the restricted list.
This ensures developers can install only the MCP servers your organization approves.
Preparing for Authenticated Registries
The MCP registry spec recently added support for authentication directly on registry endpoints.
Obot v0.14 already supports this.
When VS Code and other clients adopt the feature, Obot will be able to present personalized registry views, such as:
- Engineering: 12 internal + OSS servers
- Marketing: 3 approved servers
- SRE: advanced/internal servers
- Experimental teams: pre-release or prototype servers
This enables true least-privilege server discovery across your entire organization.
Why MCP Registry Support Matters
This feature makes the MCP ecosystem more secure, more manageable, and more aligned with enterprise needs:
- Centralized governance of the server catalog
- Consistent developer experience across VS Code, Copilot, and other MCP clients
- Principle-of-least-privilege by default
- Zero trust–friendly workflows
- Scalable visibility controls for large orgs
Obot becomes the authoritative source of what your organization should and should not run.
Getting Started with Obot v0.14
MCP Registry Support is available today.
- Watch the demo video above.
- Visit our documentation for setup instructions:
- Explore the code on GitHub:
Don’t forget to give us a star while you’re there!
To run Obot locally:
docker run -d \
--name obot \
-p 8080:8080 \
-v /var/run/docker.sock:/var/run/docker.sock \
ghcr.io/obot-platform/obot:v0.14.0
Thanks for being part of the Obot community!
We can’t wait to see how you use MCP Registry Support to bring structure, security, and clarity to your MCP ecosystem.
