ToolJet MCP
An implementation of the Model Context Protocol on the ToolJet low-code platform that enables coding agents to directly read workspace structures, create data tables and queries, and generate interface components without manually dragging and configuring step by step in a GUI.
Timeline (last 90 days)
The official ToolJet blog showcases a 'Support Ticket Sorter' app generated by a coding agent, using ToolJet MCP to build the app skeleton and TypeSafe's Jev to make the sorting judgments, with 100 synthetic tickets ultimately turned into a reviewable processing queue.
ToolJet MCP is an implementation of this protocol on the ToolJet low-code platform, enabling coding agents to directly read the workspace structure, create data tables and queries, and generate interface components.
ToolJet MCP ultimately generated 1 page, 4 PostgreSQL tables, 21 queries, and 29 components, with 0 code files requiring maintenance, and went through 2 rounds of fixes.
A failure occurred on the first click of Sort because the query parameters were not declared in each query's options, causing the parameter interpolation to resolve to an empty string and the run id to become undefined; after adding the parameter declarations to all queries, it returned to normal.
All Facts (4)
ToolJet MCP is an implementation of this protocol on the ToolJet low-code platform, enabling coding agents to directly read the workspace structure, create data tables and queries, and generate interface components.
50%UnverifiedToolJet MCP ultimately generated 1 page, 4 PostgreSQL tables, 21 queries, and 29 components, with 0 code files requiring maintenance, and went through 2 rounds of fixes.
50%UnverifiedThe official ToolJet blog showcases a 'Support Ticket Sorter' app generated by a coding agent, using ToolJet MCP to build the app skeleton and TypeSafe's Jev to make the sorting judgments, with 100 synthetic tickets ultimately turned into a reviewable processing queue.
50%UnverifiedA failure occurred on the first click of Sort because the query parameters were not declared in each query's options, causing the parameter interpolation to resolve to an empty string and the run id to become undefined; after adding the parameter declarations to all queries, it returned to normal.
50%