Where it fits
Make users who want their existing scenarios available as tools in an assistant.
- List the scenarios available to an assistant.
- Run a scenario with inputs.
- Check a scenario's result from the conversation.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
Skills that pair with Make
These skills cover adjacent tasks, matched by purpose and the work each one describes.
Builds and deploys an MCP server from an OpenAPI or Swagger spec with the mcp-use TypeScript SDK. Use it when the user wants to turn an OpenAPI spec into an MCP server, make an API usable from Claude or ChatGPT, wrap a Swagger doc as MCP tools, expose a REST API to an LLM, or generate MCP tools from a spec, including when they attach an openapi.yaml, openapi.json, or swagger.json file.
Keeps multi-step agent work on a file-based plan, holding task_plan.md, findings.md, and progress.md on disk while lifecycle hooks feed relevant planning context into the session. Recovery by itself only consults those project planning files. When explicitly asked, session-catchup.py with --metadata reads local agent session records from the same project and reports aggregate counts; --replay can add bounded excerpts wrapped in nonces. A gated mode may request continuation on hosts that support it, never executes commands written in Markdown, and nothing is uploaded over the network.
Turn a vague wish into an actionable, checkable deliverable by asking only for the constraints and acceptance criteria that affect execution. Use when the goal, scope, or definition of done is unclear.
No skills found
Try a different search term or clear the filters.
Local stdio via npx
Set MAKE_API_KEY with scenarios:read and scenarios:run scopes, plus MAKE_ZONE and MAKE_TEAM. The hosted endpoint at https://mcp.make.com is separate and answers 401 without a connection.
- Create a Make API key
Generate a key in your Make profile with the scenarios:read and scenarios:run scopes.
- Add the stdio server
Add command npx with args -y @makehq/mcp-server, and set MAKE_API_KEY, MAKE_ZONE (for example eu2.make.com) and MAKE_TEAM in the environment.
- Reload and list scenarios
Restart the client and confirm the Make scenarios appear as tools.
Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.
Endpoint and configuration
The installer uses the server name make. If you add the endpoint by hand, keep the same name so the guide and your config match.
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
- 1Open the tool list.
Restart the client or start a new session. Confirm that
makeappears and that the tools match the provider documentation. - 2Run one small request.
Start with: List the scenarios available to an assistant. Check the result before you give the server more access.
- 3Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. The provider page was available when we checked.
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
- The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
- The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
- Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Before you connect
- The provider can see the requests and data your agent sends through the server.
- Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
- Use project scope for repository-specific servers; use global scope for personal tools.
- Remove the server and revoke its token when you stop using it.
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.
Provider source
Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.
Make repositoryhttps://github.com/integromat/make-mcp-server