Integrator MCP Server (legacy)

What is Integrator MCP Server (legacy)?

A Model Context Protocol server that enables Integrator scenarios to be utilized as tools by AI assistants. This integration allows AI systems to trigger and interact with your Integrator automation workflows.

How to use Integrator MCP Server (legacy)?

Install via npx and configure the environment variables INTEGRATOR_API_KEY and INTEGRATOR_TEAM in your MCP client settings (e.g., claude_desktop_config.json). The server then connects to your Integrator account and exposes on-demand scenarios as callable tools.

Key features of Integrator MCP Server (legacy)

• Connects to Integrator and identifies "On-Demand" scenarios.
• Parses and resolves input parameters with meaningful descriptions.
• Allows AI assistants to invoke scenarios with correct parameters.
• Returns scenario output as structured JSON.
• Turns automation workflows into callable AI tools.

Use cases of Integrator MCP Server (legacy)

• Trigger Integrator workflows directly from an AI assistant via natural language.
• Expose complex, multi-step automations to AI systems without rewriting logic.
• Enable bidirectional communication between AI assistants and existing automation pipelines.
• Automate data processing or integration tasks by invoking Integrator scenarios from AI conversations.

FAQ from Integrator MCP Server (legacy)

Which scenarios can be used with this server?

Only scenarios configured with "On-Demand" scheduling are detected and exposed as tools.

What are the prerequisites for running the server?

You need NodeJS, an MCP client (such as the Claude Desktop App), and an Integrator API Key with the scenarios:read and scenarios:run scopes.

How do I obtain an API key and team ID?

Generate an API key in your Integrator profile. Find the team ID in the URL of your Team page.

What is the origin of this project?

This server is a fork of software originally developed by Make (MIT licensed). It has been modified and is maintained by Boost.space.

Does the server store any data locally?

The server acts as a proxy between the MCP client and the Integrator API; no local storage of scenario data is described in the README.