Bring Low Code
to CrewAI
Learn how to connect ToolJet to CrewAI and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the ToolJet MCP Server?
Connect your ToolJet workspace to any AI agent to interact with your internal databases and automate business logic through natural language.
What you can do
- Database Exploration — List all available tables within your ToolJet Database to understand your data structure.
- Advanced Querying — Execute SQL SELECT queries on your tables to retrieve specific records, filter data, and generate insights.
- Data Entry — Insert new rows into your database tables directly from the chat interface using structured JSON data.
- Workflow Automation — Trigger complex ToolJet Workflows via webhooks, passing custom payloads to start automated business processes.
How it works
- Subscribe to this server
- Enter your ToolJet API Key (and optional Host URL for self-hosted instances)
- Start managing your internal data and workflows from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Developers — Quickly query internal databases or trigger CI/CD workflows without leaving the code editor.
- Operations Teams — Update records or start business processes using natural language instead of complex UIs.
- Data Analysts — Explore ToolJet Database tables and run ad-hoc queries to verify data integrity.
Built-in capabilities (4)
Insert a new row into a ToolJet Database table
List all tables in the ToolJet Database
Use this for reading data (SELECT). Perform a SQL query on a ToolJet Database table
Trigger a ToolJet Workflow via Webhook
Why CrewAI?
When paired with CrewAI, ToolJet becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ToolJet tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
ToolJet in CrewAI
ToolJet and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ToolJet to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ToolJet in CrewAI
The ToolJet MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
ToolJet for CrewAI
Every tool call from CrewAI to the ToolJet MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I perform complex SQL joins using this server?
Yes, the query_table tool allows you to execute SQL queries. As long as the tables exist in your ToolJet Database and your organization ID is correct, you can perform SELECT statements including joins and filters.
How do I trigger a specific automation I built in ToolJet?
You can use the trigger_workflow tool. You will need the workflow_id and can optionally provide a JSON payload to pass data into the workflow's entry point.
Can I see the list of all my database tables?
Absolutely. Use the list_tables tool to retrieve a complete list of all tables currently configured in your ToolJet Database workspace.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Avaza
11 toolsUnified project management, time tracking, and invoicing via Avaza — orchestrate professional services natively via AI.
Papermark (Docsend Alternative)
6 toolsSecurely share documents, track engagement, and manage links with Papermark — the open-source DocSend alternative for your AI agent.
GivingFuel
10 toolsRetrieve donation orders, track registrants, and oversee fundraising pages via AI agents with GivingFuel.
Forj
12 toolsManage community members, groups, and activity via AI agents with Forj (formerly Mobilize).