Last September we repositioned this repository as an AI-native internal application and agent builder. This is the follow-up: what shipped since, and what it means for the Community Edition.

We introduced AI app generation in February 2025. It worked for simpler applications, but it was not reliable enough for the complexity of real business software, and it understood only a small part of the platform. We could have kept patching it. Instead we rebuilt the experience.

ToolJet is now a platform where the same application can be built in three ways, and you can move between them at any point.

Build from the coding agent you already use.

The new ToolJet MCP lets Claude Code, Codex, Cursor and other MCP-compatible agents create, inspect and modify ToolJet applications directly. Agents build against ToolJet's first-party contracts, so they work from the platform's real schemas instead of guessing at them, and operations run on your own model subscription rather than drawing down ToolJet AI credits.

Because MCP servers compose inside a single agent, workflows open up that were not possible before. An agent can read a design and its design system through the Figma MCP, then build the working application in ToolJet. The same applies to any other source the agent can reach.

ToolJet no longer dictates where the building happens. It provides the structured application platform and the production runtime underneath whichever tool you build from.

ToolJet MCP is currently in beta. Setup guide: https://docs.tooljet.com/docs/build-with-ai/mcp/overview

A rebuilt AI Builder

The in-product builder now generates complete applications, including pages, interfaces, queries, data connections and application logic, and it works across ToolJet's full integration library. It builds against the databases, APIs and SaaS tools your business already runs rather than generating an isolated demo on sample data. Describe what you need, refine it in natural language, and switch to the visual builder or to code whenever you want.

Governance

Giving agents more power to build software raises the obvious question of control. The new Governance MCP brings ToolJet's existing governance into agent-driven workflows, so authentication, permissions and role-based access continue to apply to what agents build, across Cloud, VPC and self-hosted deployments.

What this means for this repository

The Community Edition remains the foundation of ToolJet and continues to be actively maintained.
All core platform changes continue to be committed upstream to this repository.
The README is being updated to document the MCP and coding-agent path alongside the visual builder.
Contributions here strengthen both CE and ToolJet AI, exactly as before.

Full announcement