Content
# Make.com MCP Connector
MCP connector (extension for Claude Desktop), which connects Claude with **Make.com**
(Integromat) — list, run, enable/disable and track scenarios
(scenarios / automations).
> ⚠️ **Private repo.** Configuration contains Make API token — do not make it public.
> The token is NOT in the code — it is entered during installation (see below).
Separate from the Basecamp connector on purpose — both work in parallel in Claude Desktop,
without interfering with each other. This project shares the proven infrastructure of the Basecamp connector
(corporate TLS fix, robust stdio start), but with authentication via Make API token
instead of OAuth.
## Structure
| File | Role |
|---|---|
| `server.js` | Entire logic — tools + MCP server |
| `manifest.json` | Extension manifest (version, starter, tool list, configuration) |
| `package.json` | Dependencies |
## Tools (briefly)
- **Organization/teams:** `make_list_organizations`, `make_list_teams`
- **Scenarios:** `make_list_scenarios`, `make_get_scenario`
- **Actions:** `make_run_scenario` (run now), `make_start_scenario` (enable), `make_stop_scenario` (disable)
- **Tracking:** `make_list_executions` (history), `make_get_execution` (details for one execution)
- **Data stores:** `make_list_data_stores`, `make_get_records`, `make_add_record`, `make_update_record`, `make_delete_record` (delete only specific keys)
- **Miscellaneous:** `make_open_in_browser`
## Setup (for users)
Users **do not install anything additional** — Claude Desktop comes with a built-in Node.
1. Download the latest `.mcpb` from **Releases** (or from the company folder).
2. Claude Desktop → Settings → Extensions → **Install from file** → select `.mcpb`.
3. During installation, fill in:
- **Make API token** — created in Make: avatar top right → *Profile → API / MCP access → Add token*.
Give it scopes: `scenarios:read`, `scenarios:write`, `scenarios:run`, `teams:read`, `organizations:read`, `datastores:read`, `datastores:write`.
- **Region (zone)** — seen in the URL of the Make dashboard (e.g., `eu1.make.com` → enter `eu1`).
Possible: `eu1`, `eu2`, `us1`, `us2`. Wrong region gives access error even with a valid token.
- **Organization ID / Team ID** (optional) — if you have only one organization, it is selected automatically.
4. Full Quit + restart of Claude Desktop.
## For developers
```
npm install # downloads dependencies (required for build/test)
node --check server.js
```
Local start (environment variables required):
```
# PowerShell
$env:MAKE_API_TOKEN="…"; $env:MAKE_ZONE="eu1"; node server.js
```
Useful environment variables:
| Variable | Meaning |
|---|---|
| `MAKE_API_TOKEN` | API token (required) |
| `MAKE_ZONE` | Region: `eu1` (default), `us1`… or full host |
| `MAKE_API_BASE` | Full override of the base URL (optional) |
| `MAKE_ORG_ID` | Default organization |
| `MAKE_TEAM_ID` | Default team |
## Building `.mcpb` (manually)
```
npm install
npx @anthropic-ai/mcpb pack . Make-mcp-<version>.mcpb
```
`.mcpb` is a zip with `manifest.json` in the root. `.mcpbignore` excludes `.git`, `.env`, etc.
## Releasing a new version
1. Bump the version in `manifest.json` **and** `package.json`.
2. Build `.mcpb` and upload to Releases.
## Make API — notes
- Base URL: `https://{zone}.make.com/api/v2`
- Authentication: header `Authorization: Token <token>`
- Documentation: https://developers.make.com/api-documentation
