NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1710 by repository stars
Latest stable
v0.28.0
Last release 12 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 58 of 58 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
3023 releases · first in 2024
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
This addresses moving Enforcement Events into Inventory, supplying an option to add beta tag on a tab as well as offset options for tooltip popovers (
fix: move enforcement events (#8325)
This addresses moving Enforcement Events into Inventory, supplying an option to add beta tag on a tab as well as offset options for tooltip popovers (in this case, it is to make sure the popover is appropriately adjusted when the beta tag is there). This also addresses some unrelated test specs with unhandled calls by adding mock handlers and some binding warnings due to passing non-reactive props to the component in their test cases.
This is a patch release for v0.26.2. It repairs static configuration on connections migrated during the v0.26 upgrade, restores the MCP server Tools a
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This is a patch release for v0.26.2. It repairs static configuration on connections migrated during the v0.26 upgrade, restores the MCP server Tools and Troubleshooting tabs, and fixes OAuth with ChatGPT CIMD clients and with servers such as AWS Knowledge MCP.
If you are upgrading from v0.25.x, you can upgrade directly to v0.26.3 and follow the Upgrade Notes in v0.26.2.
frontend identity unavailable.private_key_jwt client assertions addressed to the scoped token endpoint it advertises for each vMCP (/oauth/token/{mcp_id}).Content-Type and Accept headers that the MCP specification requires when it probes a remote server during OAuth setup. Servers that reject requests without these headers, such as AWS Knowledge MCP, no longer fail OAuth metadata sync over and over with resource is required but not provided.${API_HOST} correctly again.Full Changelog: https://github.com/obot-platform/obot/compare/v0.26.2...v0.26.3
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
We're excited to announce the v0.26.2 release of the Obot Platform. This is the upgrade release for v0.26: existing v0.25.x installations can now upgr
We're excited to announce the v0.26.2 release of the Obot Platform. This is the upgrade release for v0.26: existing v0.25.x installations can now upgrade. On startup, Obot migrates existing MCP servers and composite servers to virtual MCPs (vMCPs) while keeping the access users already have. If you maintain catalogs in Git, you need to update them yourself, as described in the Upgrade Notes.
[!IMPORTANT] Existing installations can now upgrade to v0.26. The v0.26.0 and v0.26.1 notes said that existing installations should not upgrade, and that upgrade support would follow in a patch release. This is that release. Upgrade directly from v0.25.x to v0.26.2, and follow the Upgrade Notes below. They include required steps for Kubernetes deployments with more than one replica and for anyone who maintains catalogs in Git.
If you are upgrading from v0.25.x, this release includes everything from v0.26.0 and v0.26.1. Read both sets of notes. The main changes are:
The upgrade to v0.26.2 runs a data migration on startup, so it needs extra care when Obot runs with more than one replica.
If you run Obot on Kubernetes, follow these steps. They apply whether you use helm directly or a continuous deployment system.
Recreate in the same change. In the Helm chart, use the updateStrategy value. If you use the helm CLI directly, also pass --server-side=false so Helm can remove the rollingUpdate config.Recreate override. Do not scale above one replica until the migration and startup have finished.If you run Obot as a single-node Docker deployment, follow the normal upgrade procedure.
See #8093 for details or to comment with follow-up questions.
During the upgrade, Obot creates a vMCP for every MCP server that an access control rule explicitly exposes. Each vMCP gets the same access as the original server, enforced through profiles on the vMCP. The upgrade does not grant any user or group new access.
Installations with broad access rules will see many new vMCPs, because every MCP server covered by a rule gets one. This applies to both composite and non-composite servers. After the upgrade, administrators can review these vMCPs and delete any that users no longer need. If users still need a server, keep its vMCP.
This release changes the catalog configuration schema and replaces composite catalog entries with vMCPs. If you maintain your own catalog sources in Git, you must update them using the Obot CLI from this release. Composites created in the Obot UI are converted on startup and need no further action.
All the command run in these steps need the base URL of the Obot instance you are connecting to. The easiest way to do this is to
export OBOT_BASE_URL=https://obot.example.com
Complete the deployment upgrade using the steps above and confirm that Obot starts. Use the new Obot CLI and work from a local checkout of your catalog repository. Repeat the remaining steps for each catalog.
Optional: generate vMCP definitions for migrated composites. If your catalog had composite entries, you can have the catalog take over management of the migrated vMCPs. Sign in as an administrator, let the catalog sync finish, and generate replacement definitions:
obot mcp generate-vmcp-catalog https://github.com/example/catalog --mode dir ./vmcps
Use the source URL configured in Obot, including any branch path. The command writes one YAML file for each migrated vMCP waiting to be adopted. It does not change anything in the Obot instance. Resolve any Skipping vMCP messages before you continue. You an also include --format json if you would like the output to be in JSON instead of YAML.
Remove composite definitions. Catalog sync no longer supports runtime: composite. These entries should be removed from the catalog.
Convert the remaining catalog YAML: The remaining catalog entries need to be migrated to the new schema. Use the following command:
obot mcp convert-catalog .
This updates files in place. It moves legacy environment variables and configurable headers into the unified config schema and removes serverUserType fields. Similar to the above, you an also include --format json if you would like the output to be in JSON instead of YAML.
Validate the catalog:
obot mcp validate-catalog .
Publish and sync. Push the updated catalog to its configured branch, then click Sync under Admin > MCP Servers > Click the Sources tab. Ensure the Git Source URLs contains no errors.
Optional: confirm adoption. Run obot mcp generate-vmcp-catalog-yaml again for the same source. If catalog sync was successful and all vMCP were properly adopted, it reports that none are waiting for catalog sync.
See #8094 for details or to comment with follow-up questions.
The REST endpoints for managing standalone MCP servers have been removed, because vMCPs now cover that work. This includes the server management routes under /api/mcp-servers, /api/mcp-server-instances, and /api/mcp-catalogs/{catalog_id}/servers. The Obot UI already uses the vMCP APIs. If you have scripts or automation that call these endpoints, update them to use vMCPs before you upgrade.
secretBinding, so values such as access tokens can come from a Kubernetes Secret instead of clear text.OBOT_SERVER_PRODUCT_ANALYTICS_MODE. on and off have the same effect as opting in or out in the UI, and the consent prompt and setting are hidden. The default, consent, keeps the current behavior of asking an administrator in the UI.Full Changelog: https://github.com/obot-platform/obot/compare/v0.26.1...v0.26.2
Nothing published for this version
One column per month.