Skip to content

v0.12.0

Latest

Choose a tag to compare

@cjellick cjellick released this 17 Oct 01:28
· 10 commits to main since this release
7649be2

We’re excited to announce the release of Obot MCP Gateway v0.12.0! This release brings powerful new roles, expanded audit capabilities, and a wide range of UI, backend, and integration improvements.

✨ Big Updates

  • Auditor & Owner Roles: New roles separate system management from sensitive data access — only Auditors can view all server and chat details, while only Owners can assign the Auditor role. Admins can no longer see these sensitive details unless they’re also assigned as Auditors.
  • Admin Dashboard Upgrades: New "Deployments and Connections" dashboard for easily visualizing and operating on MCP servers in bulk.
  • Okta Group Support for Access Control Rules: You can now use Okta groups when configuring Access Control Rules, making it easier to manage permissions with your existing identity provider.
  • Customizable Remote MCP Connections: Authors can now configure Remote MCP entries with user-supplied or static HTTP headers, and inject user-supplied values into templated URLs.
  • Expanded Power User Capabilities: Power Users and Power User Plus now have access to usage stats and audit log metadata (excluding sensitive data) for their MCP servers.
  • Kubernetes & Helm Enhancements: Helm charts now support affinity, tolerations, nodeSelector, and Kubernetes-recommended labels for smoother deployment and upgrade of Obot.

🛠 Other Notable Improvements

  • UI/UX Polish: Refined navigation, dynamic chevrons, improved table columns, and enhanced project sharing styling.
  • Sensitive Data Handling: Better masked value display and multi-line support in sensitive fields.
  • Database & Logging: Improved DB logging and clarified requirements.
  • Bug Fixes: Numerous fixes for table filtering, sorting, admin tools, and Safari-specific UI issues.
  • Documentation: Expanded guides, including improved Entra setup walkthroughs.

⚠️ Important Upgrade Notes

Please review the following before upgrading:

Transition to Owner Role

The new Owner role now sits above the Admin role as the most privileged role in the system. To leverage it's ability to assign the Auditor role, you must assign one or more initial Owners via the OBOT_SERVER_AUTH_OWNER_EMAILS environment variable. This has the same semantics as the OBOT_SERVER_AUTH_ADMIN_EMAILS environment variable.

Embedded DB no longer the default for Helm installs

For Helm installs, Obot no longer defaults to a built-in Postgres database. An external database is required for production setups, but the embedded database remains available for evaluation. You must either provide a database connection string via config.OBOT_SERVER_DSN, or explicitly opt into the embedded database for testing by setting dev.useEmbeddedDb to true.

If you are upgrading and were previously using the embedded database, you must set the dev.useEmbeddedDb to true when you upgrade.

Okta users have to update their issuer URL

For Okta users, after updating to this release, you will need to modify the Issuer URL in the Okta auth provider configuration. This is due to our new support for Okta groups.

You must set it to https://.okta.com with no path in the URL.
See https://docs.obot.ai/configuration/auth-providers#okta-enterprise-only for more information, as there are some settings you must tweak in your Okta workspace in order for Obot to work with the groups in your directory.

If you find that you are unable to log in to adjust this setting, restart Obot with the environment variable OBOT_SERVER_FORCE_ENABLE_BOOTSTRAP=true so that you can log in as the bootstrap user again in order to change the setting.

📜 Full changelog

Full Changelog: v0.11.0...v0.12.0

🚀 Getting Started

  • Try the live demo: chat.obot.ai
  • Install on Docker:
    docker run -d --name obot -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock \
    ghcr.io/obot-platform/obot:latest
  • For more, see our Documentation

🙌 Thanks to Our Contributors

Finally, a special welcome and thank you to @nlamirault for their first contribution to this release!