MCP server for interacting with Integrator automations
Integrator MCP server exists for a simple reason — assistants are far more useful when they can act on Integrator directly instead of describing what you should do. MCP server for interacting with Integrator automations.
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.
Once Integrator is connected, these are the calls the assistant has available:
Prerequisites — The Prerequisites tool exposed by this serverInstallation — To use this server with the Claude Desktop app, add the following configuration to the "mcpServers" section of your claude_desktop_config.json: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.
You will need 2 environment variables: INTEGRATOR_API_KEY, INTEGRATOR_TEAM. 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.
scenarios:read and scenarios:run scopesPlenty 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. Integrator's toolset — Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by boostspace; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Prerequisites | The Prerequisites tool exposed by this server. |
| 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>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
scenarios:read and scenarios:run scopes| Variable | Description | Required |
|---|---|---|
| INTEGRATOR_API_KEY | Credential the server authenticates with. | Yes |
| INTEGRATOR_TEAM | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.