ToolJet MCP Server

Connect ToolJet to your AI assistants

Local serverstdio

What is the ToolJet MCP server?

Connect ToolJet to your AI assistants. Exposed over MCP by the tooljet mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Empower your AI assistants with direct access to your ToolJet platform. This MCP (Model Context Protocol) integration enables AI tools like Claude, Cursor, and other MCP-compatible assistants to interact with your ToolJet instance.

ToolJet MCP is a bridge that connects AI assistants to your ToolJet platform through the Model Context Protocol. This allows AI tools to:

Its toolset

Everything the assistant can do here goes through one of these:

  • Requirements — The Requirements tool exposed by this server
  • Configuration — The Configuration tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Configuration

You will need 2 environment variables: TOOLJET_ACCESS_TOKEN, TOOLJET_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js (v14 or higher) - A ToolJet instance with admin access - An MCP-compatible AI assistant (Claude, Cursor, etc.)

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. ToolJet's toolset — Requirements, Configuration — is a fair guide to whether it matches your workflow. It is maintained by ToolJet; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the tooljet mcp server does with a few real requests.

Available tools

ToolWhat it does
RequirementsThe Requirements tool exposed by this server.
ConfigurationThe Configuration tool exposed by this server.

How to install the ToolJet MCP server

{
  "mcpServers": {
    "tooljet": {
      "command": "npx",
      "args": [
        "-y",
        "@tooljet/mcp"
      ],
      "env": {
        "TOOLJET_ACCESS_TOKEN": "your-access-token",
        "TOOLJET_HOST": "https://your-tooljet-instance.com"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js (v14 or higher) - A ToolJet instance with admin access - An MCP-compatible AI assistant (Claude, Cursor, etc.)
VariableDescriptionRequired
TOOLJET_ACCESS_TOKENCredential the server authenticates with.Yes
TOOLJET_HOSTEndpoint or connection string the server talks to.Optional

Example prompts to try

  • Use ToolJet to Requirements.
  • Use ToolJet to Configuration.

Frequently asked questions

Node.js v14 or higher, a ToolJet instance with admin access, and an MCP-compatible AI assistant.