NocoDB 2026.09.0 released on 10-09-2026
NocoDB 2026.09.0 is out now. Claude users and teams running Cloud or self‑hosted NocoDB benefit from direct connector support and a substantially expanded MCP toolset that brings workspace administration to MCP clients.
Visit the NocoDB GitHub or the official docs for full details, installation instructions, and links to the MCP and workflow documentation.
What’s in this release
- NocoDB in Claude Connectors — bases can be connected from the Claude Connectors directory so Claude (and other connector clients) can access a base without manually adding the MCP URL; connected clients may call any MCP tool allowed by the user’s role and the integration is available across Community Edition, Cloud Free, and Paid plans with the same role‑based permissions and audit behaviour as the API.
- MCP tools expansion — the MCP server has grown from 11 tools to 149, covering tables, fields, views, filters, sorts, workflows, interfaces, dashboards, widgets, scripts, documents, webhooks, comments, permissions, RLS, row colouring, folders, members, CSV import/export and more; each tool maps to the corresponding REST API service, enforces validation and permissions, and respects caller roles (viewer/editor/creator).
- Rich text emails in workflows — Send Email, SMTP, Gmail and Outlook nodes share a rich‑text editor supporting headings, styling, lists, colours, links with custom anchor text and insertion of workflow variables; rich text email composition is a paid Cloud feature (Plus plan and above) while the Community Edition retains MCP record tools but not the composer.
Upgrade notes
- Planned API datetime format change (not in 2026.09.0) — PostgreSQL and SQLite datetime outputs will move from second to millisecond precision in a future release; review integrations that parse datetimes and update parsers to accept a millisecond component.
- Self‑hosting hardening — Community mode hides locked sub‑features, disabled or expired API tokens are rejected, and paid field types are rejected on unlicensed deployments; check API tokens and licensing before upgrading to avoid unexpected access or feature rejections.
Share feedback or report issues on the project’s GitHub, and tell the community how you get on with the new MCP tools and workflow email editor.
