Name: Integrator (legacy)
Author: boostspace

LABSCO SUMMARY

The scenario's schedule setting is the access control.

Only scenarios set to On-Demand appear as tools, which makes the Integrator UI the place where you decide what an assistant may run — no allowlist to maintain here. The API key scopes are read and run only, so the assistant can trigger workflows but not rewrite them. This is a fork of Make's original server, maintained by Boost.space and marked legacy.

What it is

A bridge between an AI assistant and Boost.space Integrator. It connects to your account, finds the scenarios set to On-Demand scheduling, and offers each one as a callable tool with its inputs described.

What you get

Every On-Demand scenario in your team exposed as a tool, discovered automatically rather than configured by hand
Input parameters parsed and resolved, so the assistant sees meaningful parameter descriptions instead of raw field names
Scenario output returned as structured JSON, which the assistant can read and act on
Automation logic that stays in Integrator — you expose it to the model without rebuilding it

Requirements

The npm package @boostspace/integrator-mcp-server, version 0.1.4, run as npx -y @boostspace/integrator-mcp-server. Two environment variables: INTEGRATOR_API_KEY, generated in your Integrator profile with the scenarios:read and scenarios:run scopes, and INTEGRATOR_TEAM, the team id from the URL of your Team page. Node.js is the only local dependency.

Setup effort

One command plus a key — npx -y @boostspace/integrator-mcp-server, then supply credentials

See installation options

USE CASES

01

Letting an assistant trigger an existing automation

Run a scenario you already built, with the parameters filled in from the conversation.

02

Reading a workflow's result back into the chat

Scenario output comes back as structured JSON, so the assistant can use the values rather than quote them.

03

Choosing which automations are reachable

Switch a scenario to On-Demand scheduling to expose it, or off it to take it away.

BEFORE YOU INSTALL

What to know first

Requires

npx on PATH
INTEGRATOR_API_KEY in your environment

Where it runs

The documented client runs the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y @boostspace/integrator-mcp-server

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "integrator": {
      "command": "npx",
      "args": [
        "-y",
        "@boostspace/integrator-mcp-server"
      ],
      "env": {
        "INTEGRATOR_API_KEY": "<YOUR_INTEGRATOR_API_KEY>",
        "INTEGRATOR_TEAM": "<YOUR_INTEGRATOR_TEAM>"
      }
    }
  }
}

Integrator (legacy)