Announcing Obot MCP Platform v0.15.0: Gateway Re-Architecture, Custom Branding, and a Unified UX

We are excited to announce the release of Obot v0.15.0. This release includes a major architectural change to the platform, new branding capabilities, a significant UX overhaul across user roles, and a refreshed documentation experience. Check out the video below for a peek at all the new features.

Try Obot Today

⬇️ Download the Obot open-source gateway on GitHub and begin integrating your systems with a secure, extensible MCP foundation.

Gateway Re-Architecture for a More Extensible Platform

The headline architectural change in this release is a re-architecture of the Obot Gateway. We have simplified the responsibilities of the gateway so that it focuses on authentication, deployment validation, and proxying requests. This creates a cleaner separation of concerns and makes the platform easier to extend and maintain going forward.

We have written up the full technical story behind this re-architecture, the motivations, and how it positions Obot for future capabilities. You can read the detailed post by Donnie Adams here.

A Unified and Role-Aware UX

We have also made meaningful improvements to the user experience across the platform.

For admins, many of the changes are subtle but practical. For example, from the MCP server page you can now connect directly to a server. Previously, this required navigating to a different part of the application. These small changes reduce friction and keep you in one place.

The more noticeable changes come into play across different user roles. All users now share a consistent navigation structure that adapts based on their role.

• Basic users see only what they are permitted to use. They can deploy servers granted to them through the MCP registry and launch Obot Chat.
• Power Users gain the ability to create arbitrary MCP servers and view audit logs and usage information for them.
• Power Users+ see additional options for MCP Registries. This allows them to share servers with other users by granting access through the registry.

We also streamlined the server creation flow. When adding a new MCP server to a registry, you are now immediately prompted to connect to it. Previously, defining a server and connecting to it were separate steps in different parts of the app.

Overall, this release brings together what were once separate experiences. There is no longer a distinction between connector management and MCP publishing. You now have a single MCP Platform, alongside the chat experience, that works cohesively across roles.

Custom Branding for Your Obot Instance

With Obot v0.15.0, you can now brand your Obot instance to match your organization.

Admins can customize:

• Colors
• Logos
• Icons

This allows Obot to feel like a natural extension of your existing stack, rather than a generic third-party interface.

Improved Documentation

We have also overhauled the Obot documentation.

The updated docs are easier to navigate and designed to clearly explain Obot’s core concepts and key features. Whether you are just getting started or diving into more advanced use cases, the documentation should now make it easier to follow along and build with confidence.

Getting Started

That covers the highlights of Obot v0.105. To learn more you can:

• Watch the release video above.
• Visit our documentation for setup instructions:
  • https://docs.obot.ai/
• Explore the code on GitHub:
  • https://github.com/obot-platform/obot
• Or just 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.15.0

Get Started with Obot

Try Obot on GitHub · Schedule a demo · Read the docs