mcpField
I
Integrator MCP Server (legacy)

Integrator MCP Server (legacy)

Local
github.com/boostspaceProductivity0Updated 80w ago
Repository

About Integrator MCP Server (legacy)

Integrator MCP Server (legacy) exposes Integrator automation scenarios as tools for AI assistants. It discovers scenarios configured for On-Demand scheduling, describes their inputs, invokes them, and returns structured JSON results.

Key features

  1. 01Discover On-Demand scenarios
  2. 02Resolve and describe input parameters
  3. 03Invoke automation scenarios
  4. 04Return structured JSON output

Use cases

  1. 01Run Integrator workflows from an AI assistant
  2. 02Expose existing automation logic to AI systems
  3. 03Read scenario results as structured data

MCP support

Connects to an Integrator account and exposes eligible scenarios as MCP tools. It requires an API key with `scenarios:read` and `scenarios:run` scopes.

#integrator#mcp#server#automation#ai

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "integrator": {
      "command": "npx",
      "args": [
        "-y",
        "@boostspace/integrator-mcp-server"
      ],
      "env": {
        "INTEGRATOR_API_KEY": "<INTEGRATOR_API_KEY>",
        "INTEGRATOR_TEAM": "<INTEGRATOR_TEAM>"
      }
    }
  }
}
Run commandnpx -y @boostspace/integrator-mcp-server
Environment variables to set
INTEGRATOR_API_KEYSecret
INTEGRATOR_TEAM

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@boostspace/integrator-mcp-server

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

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.

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

How It Works

The MCP server:

  • Connects to your Integrator account and identifies all scenarios configured with "On-Demand" scheduling
  • Parses and resolves input parameters for each scenario, providing AI assistants with meaningful parameter descriptions
  • Allows AI assistants to invoke scenarios with appropriate parameters
  • Returns scenario output as structured JSON, enabling AI assistants to properly interpret the results

Benefits

  • Turn your Integrator scenarios into callable tools for AI assistants
  • Maintain complex automation logic in Integrator while exposing functionality to AI systems
  • Create bidirectional communication between your AI assistants and your existing automation workflows

Usage with Claude Desktop

Prerequisites
  • NodeJS
  • MCP Client (like Claude Desktop App)
  • Integrator API Key with scenarios:read and scenarios:run scopes
Installation

To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json:

{
    "mcpServers": {
        "integrator": {
            "command": "npx",
            "args": ["-y", "@boostspace/integrator-mcp-server"],
            "env": {
                "INTEGRATOR_API_KEY": "<your-api-key>",
                "INTEGRATOR_TEAM": "<your-team-id>"
            }
        }
    }
}
  • INTEGRATOR_API_KEY - You can generate an API key in your Integrator profile.
  • INTEGRATOR_TEAM - You can find the ID in the URL of the Team page.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.