Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Make
Overview
Description from the maker (original English)
Build, run and debug Make automation scenarios.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.make.com/v2Run this in your terminal
claude mcp add --transport http make https://mcp.make.com/v2Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"make": {
"url": "https://mcp.make.com/v2"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"make": {
"type": "http",
"url": "https://mcp.make.com/v2"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.make.com/v2Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain make.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32403 servers in this category
- Published to the registry more recently than 81% of the other 32403 servers in this category
- Basic checks equal to or better than 100% of the other 32403 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Make safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 8 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, LickityClick
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
LickityClick
by lickity.click
Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.
Computer or cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Make Skills for AI Coding Agents
Give your AI coding agent deep Make expertise — for building, explaining, running and debugging Make scenarios and authoring and operating Functions v2 through Make's MCP server, calling app Endpoints through the standalone Endpoints SDK or CLI, and securely requesting credentials for Endpoints and custom-app testing. Works with agents that read skill folders and can use the relevant interface — Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Cline, and others. For Make app development, use Make Apps Skill.
Skills
| Skill | What it does |
|---|---|
| make-scenario-reference | The conventions every tool shares — scopes, the data/remark contract, structure vs configuration, the one-save write model, and what the surface refuses to author — for when a tool answers 403 or refuses something |
| make-scenario-explore | Orienting in an account — organizations, teams, listing scenarios, explaining what one does, connection health, account-wide checks |
| make-scenario-building | Creating and editing scenarios — app and module discovery, connections, resolving account-dependent values, flow control, error handling, subscenarios, AI agents; with references and complete examples |
| make-scenario-operations | Running, activating and deactivating, reviewing and debugging executions, investigating a webhook |
| make-endpoints | Direct app actions through @makehq/endpoints-sdk or its CLI — discovery, managed connections, typed calls, complete retrieval, and approval-bound writes with readback. Endpoints are in closed beta. |
| make-functions-v2 | Authoring, testing, publishing and operating TypeScript Functions through the existing Make MCP connection, including Endpoint discovery and execution recovery. Requires Functions v2 rollout access. |
| make-credential-requests | Credential provisioning for agents using Endpoints or testing custom apps — the owner receives an authorization link and supplies secrets in Make; the agent resumes with managed connection/key IDs, not raw credentials. No scenario required. |
Creating a connection in the scenario editor remains the standard manual path. Credential Requests are the recommended secure handoff for agents; they complement that editor workflow rather than replace it.
Prerequisites
- A Make account
- For scenario skills and
make-functions-v2: access to the Make MCP server. Functions v2 also requires the curated Functions tools and team rollout access; installing the skill does not enable either. - For
make-endpoints: an approved Node.js/terminal environment, the Endpoints package, and organization access to the Endpoints beta. See setup and interfaces. Installing this skill does not install the SDK or enable the beta. - For
make-credential-requests: access to a chosen, authorized credential-request interface, with the required Make permissions and organization/team access. Verify that interface's current contract before making a request; installing a skill or plugin does not grant access. SDK/REST requests follow their own permission contracts, not the scenario MCP server's all-or-nothing OAuth bundle.
Installation
Install the skills and configure the interface they use. Scenario skills and make-functions-v2 use the same MCP server; make-endpoints uses @makehq/endpoints-sdk, which includes both the SDK and make-endpoints-cli. make-credential-requests uses the chosen authorized request interface to provision credentials, not execute app actions. Neither Endpoints execution nor credential provisioning requires building a scenario. Endpoints-only use does not require the scenario MCP server. The plugins below register that server for both scenario and Functions v2 skills; the standalone skill download can be used independently.
Option A: Plugin (recommended)
Claude Code
/plugin marketplace add integromat/make-skills/plugin install make-skills@make-marketplace
Cursor — Team Marketplace: import integromat/make-skills and install make. The plugin registers the MCP server (/cursor).
Codex
codex plugin marketplace add integromat/make-skillsThen open the plugin directory, select the Make marketplace, and install make. If the MCP server is not registered automatically, add it manually:
codex mcp add make --url https://mcp.make.com/openaicodex mcp login make
Option B: Download the skills
Upload the zips to your agent (Claude Cowork, Claude Chat, and similar) or unzip them into its skills directory:
| Skill | Download |
|---|---|
| Bundle of all the skills | Download |
| Scenario Reference | Download |
| Scenario Explore | Download |
| Scenario Building | Download |
| Scenario Operations | Download |
| Make Endpoints | Download |
| Functions v2 | Download |
| Make Credential Requests | Download |
Skills directories, for agents that read skills from disk:
| Agent | Skills directory |
|---|---|
| Codex (project) | .agents/skills/ |
| Codex (global) | ~/.agents/skills/ |
| Claude Code | .claude/skills/ |
| Cursor | .cursor/skills/ |
| Windsurf | .windsurf/skills/ |
| Cline | .cline/skills/ |
| Generic | .agents/skills/ |
ChatGPT does not use a local skills directory. Install the Make plugin or use the skill-upload flow supported by the selected ChatGPT experience; configure and authenticate its Make connection separately. Unzip each downloaded skill so its folder directly contains SKILL.md, references/ and examples/.
Add the MCP server manually for scenario and Functions v2 skills
Skip this if a plugin registered it. Each platform has its own endpoint, over HTTP:
| Platform | MCP URL |
|---|---|
| Claude Code | https://mcp.make.com/claude |
| Cursor | https://mcp.make.com/cursor |
| OpenAI Codex | https://mcp.make.com/openai |
claude mcp add --transport http make https://mcp.make.com/claudeclaude mcp list
For any other agent, add the matching URL to its JSON MCP config.
On first use, authenticate through Make's OAuth consent screen. Follow the tool's authorization challenge to grant its required access area. Functions v2 uses Build & Run; tool availability and team rollout access are separate from OAuth consent.
Verify the skill and connection
After installation and sign-in, refresh the client's available skills and tools (restart the client if needed). Use this read-only check before creating anything:
Use the make-functions-v2 skill. Check the Make connection, call environment_get, and show the available
organizations and teams so I can select the target. Confirm that function_list, function_endpoint_list and
function_endpoint_types are available. Do not create or run a Function yet.
The skill being discoverable, MCP being authenticated, the required tools being present, and access to the selected team are separate checks. For scenario work, use make-scenario-explore and check scenario_list instead. Reuse the configured Make connection; adding a duplicate does not grant missing access.
Functions that call Endpoints also need organization access to Endpoint execution and available generated Endpoint types. Discover the selected team's Endpoints, then retrieve their types before authoring calls. If no compatible Connection exists, create one in Make or use an available, authorized Credential Requests workflow. Complete authorization in Make, then repeat Endpoint discovery; never paste provider secrets into an agent conversation. See Functions access and discovery.
Troubleshooting
| Issue | Solution |
|---|---|
| MCP server not connecting | Confirm the server is configured, complete OAuth sign-in, then refresh tools; check network connectivity if connection still fails |
| MCP permission denied / 403 | Follow the challenge for the required access area and confirm access to the target team/resource |
| An MCP tool refuses a write | Read the refusal and the current tool contract; use the Make editor for capabilities the tool explicitly does not support |
| Endpoints SDK/CLI access failure | Check the selected key/zone, Make scopes, team access and provider connection separately; the MCP full-scope-bundle rule does not apply |
| Functions tools missing | Confirm the client has refreshed its catalog and the account/team has Functions rollout access. Installing the skill does not enable tools. |
| Functions Endpoint availability unavailable | Ask the administrator to check organization Endpoint execution access and upstream availability. This is separate from Functions rollout and OAuth consent; do not assume the catalog is empty. |
| Endpoint types unavailable | Discovery may succeed while generated types are unavailable. Report the returned status and stop authoring the affected dependency. |
| Skill not found | Check the installation scope and folder layout, then refresh/restart the client. Updating the repository does not update a previously copied skill. |
| Endpoints execution unavailable | Confirm organization beta/runtime access; local catalog discovery and package installation do not enable execution |
Contributing
Open pull requests against `main` — that's the trunk. Use squash merges an
Only the beginning is shown; read the rest in the repo