ToolJet MCP. Query, insert & automate data tasks via AI chat.
ToolJet allows your AI agent to become a backend developer for your own systems. It connects directly to internal databases so you can run SQL queries, insert records, or trigger complex business workflows—all through natural language conversation. Stop leaving the chat window to manage data; start doing it right where you are.
Give Claude and any AI agent real-world access
You can ask the agent what database tables exist without knowing their names.
The agent executes SQL SELECT statements to filter, sort, and retrieve specific records from your tables.
You can instruct the agent to insert brand-new rows of information into a database table using JSON details.
The agent triggers complex, multi-step workflows within ToolJet by sending a simple webhook call.
Ask an AI about this
Waiting for input…
What AI agents can do with ToolJet: Database & Workflow Ops (4 Tools)
Use these four specific tools—list tables, query, insert rows, and trigger workflows—to perform structured operations on your internal data directly through your AI client.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ToolJet MCPInsert Row
Adds a completely new row of data into any specified ToolJet Database table.
List Tables
Retrieves a list of all available tables within the connected ToolJet database for...
Query Table
Executes specific SQL SELECT queries against your data to retrieve filtered records...
Trigger Workflow
Initiates a complex ToolJet Workflow process by sending a webhook payload, starting...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ToolJet, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ToolJet. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Dashboard Fatigue
Today, if you need to check data or update records, the process involves jumping through hoops. You open the database UI to list tables, then switch to a query editor and write SQL (or run a pre-built report). If that doesn't work, you copy key IDs into a separate spreadsheet, manually calculate what needs changing, and finally go back to another dashboard just to hit 'Save.'
With this MCP, the entire sequence collapses. You tell your agent exactly what you need—for instance, 'Find all users in Chicago who haven't logged in for 90 days.' The agent handles the `query_table` instantly and gives you the list. No clicks, no context switching, just the answer.
ToolJet MCP: Database & Workflow Ops
You eliminate manual data entry entirely. Instead of opening a form to record new leads or product updates, you simply prompt your agent to use `insert_row`, giving it the required details in conversation. You also skip running repetitive scripts by having the agent call `trigger_workflow` for complex tasks.
Your AI client now has hands—it can read, write, and act on your business data immediately. It’s a direct bridge from thought to execution.
What ToolJet MCP does for your AI
This MCP lets any AI client connect to your private ToolJet database and automation layer. You don't have to write code or navigate a clunky UI just to check an order status or update a customer record. Instead, you tell your agent what you need—like 'Show me all pending orders for last week'—and it handles the structured interaction with your data tables.
The system executes the query and hands back clean results instantly. It also lets you kick off full business processes by triggering specific workflows, passing custom details like user IDs or product codes when needed. Because Vinkius manages this catalog connection, you get access to all these capabilities from one place, letting your agent actually perform actions on behalf of your business.
019e38fd-a9aa-7186-92dc-5595bc64f461 How to set up ToolJet MCP
The bottom line is you get structured, automated access to your business logic without writing boilerplate code.
First, subscribe to this MCP and provide your unique ToolJet API Key (and optional self-host URL).
Next, tell your AI agent what you need done—for example, 'Get me all users who signed up last month' or 'Reset the billing status for user 123'.
The system converts that request into a database query or workflow trigger and returns the resulting data or confirmation message to your chat.
Who uses ToolJet MCP
This MCP is essential for operations teams and data analysts who spend too much time jumping between spreadsheets, dashboards, and database UIs just to answer simple questions or update records. It's for the developers tired of writing repetitive boilerplate code.
Runs ad-hoc queries on specific tables to verify data integrity or pull subsets of information needed for reports, without needing a BI tool.
Updates customer records, flags processes, or starts automated business procedures using natural language instead of clicking through complex web dashboards.
Tests database interactions or triggers CI/CD workflows directly from the chat interface while working in their IDE.
Benefits of connecting ToolJet MCP
Stop switching contexts. You can run complex reports or check specific records using query_table right inside your chat window, eliminating the need to open a separate SQL client.
Handle routine data entry immediately. Instead of filling out a web form, you just ask your agent to use insert_row, providing structured JSON details for instant record creation.
Automate entire processes from conversation. Use trigger_workflow to kick off complex backend logic—like sending an onboarding email or updating inventory—with a single command.
Quickly map your data structure using list_tables. This lets you understand exactly what's in the database before writing any query, saving hours of guesswork.
The whole thing works natively across multiple platforms. You connect once to Vinkius and get this powerful database access no matter which AI client you prefer.
ToolJet MCP use cases
Investigating a delayed payment status
An operations manager needs to know why an order is stuck. They ask their agent, 'What are the details for pending orders in organization X?' The agent uses query_table and returns exactly two records with notes on the delay.
Onboarding a new user's account data
A developer needs to manually create test accounts. They tell their agent, 'Insert a new user for Jane Doe with department Marketing.' The agent uses insert_row and guarantees the record is structured correctly.
Running an end-of-month reconciliation
A data analyst needs to check if all regional dashboards are up to date. They ask their agent, 'List all available tables' first, then run a targeted query_table across inventory and orders to spot discrepancies.
Resetting a client's access after departure
An ops team member needs to execute a complex off-boarding procedure. They ask their agent to 'Trigger the full user deactivation workflow for ID 501.' The agent uses trigger_workflow and confirms the process started successfully.
ToolJet MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating it like a general chat bot
Asking, 'Hey, tell me about your database,' and expecting conversational knowledge instead of structured data. The agent can't answer vague questions.
Always ask for specific actions using the tools. Instead of asking generally, use list_tables first to understand structure, then follow up with a precise request like 'Run a query on the orders table where status is pending'.
Trying to write code manually
Writing out a complex SQL SELECT statement in your prompt when you just need simple filtering. This is verbose and error-prone.
Let the agent use query_table. You only need to describe the desired outcome naturally, and the MCP handles turning that into optimized SQL.
Forgetting the workflow step
Thinking data retrieval (reading) is enough. Missing the point that sometimes you have to kick off an action (writing/automating) after finding data.
Remember that if your goal is a change in state—like sending an alert or updating inventory—you need to use trigger_workflow after confirming the necessary details.
When to use ToolJet MCP
Use this MCP if your primary bottleneck is accessing, modifying, or acting on structured data defined by existing business logic. If you are in a role that needs to move from 'What does my database contain?' to 'I need the system to do X based on Y data,' this is what you need. This tool's strength is translating natural language intent into precise backend operations using query_table for reading, and both insert_row and trigger_workflow for writing or automating.
Don't use this if you just want the AI to summarize a document, brainstorm ideas, or generate creative text. For those tasks, a general-purpose language model is fine. You need this when your conversation needs to result in a guaranteed change of state within an external system.
Frequently asked questions about ToolJet MCP
How does the ToolJet MCP handle sensitive data? +
The connection requires you to provide an API key for controlled access. The agent only executes commands (like query_table or insert_row) based on your explicit prompt, ensuring all operations are tracked and constrained by your setup.
Does the ToolJet MCP support complex filters? +
Yes. When you use query_table, the agent generates structured SQL that supports advanced filtering, joining tables (if necessary), and sorting data to get precise results.
Can I use this MCP if my ToolJet instance is self-hosted? +
Absolutely. The setup process allows you to provide an optional Host URL, making it compatible with your private or self-managed instances.
What types of workflows can the ToolJet MCP trigger? +
The trigger_workflow tool executes any workflow defined within your ToolJet environment. These processes are limited only by the logic and steps you've built into ToolJet itself.
Is the ToolJet MCP just for reading data? +
No, it’s far more powerful than that. You can read using query_table, write using insert_row, and automate processes using trigger_workflow.