Hosted MCP server/Productivity Official

Official Make MCP server

Hosted at mcp.make.com·Streamable HTTP

Make MCP Server exposes Make scenarios to assistants as callable tools, so an agent can run an existing automation instead of rebuilding it. The documented setup is a local stdio server: run npx -y @makehq/mcp-server with a Make API key scoped for scenarios:read and scenarios:run, plus the organisation zone and team id. A hosted endpoint at https://mcp.make.com also exists and answers 401 until a connection is authorised.

mcp.make.com Streamable HTTP API key (MAKE_API_KEY) for local; OAuth on the hosted endpoint Source checked Oct 31, 2026 Server not checked yet Reviewed 2026-11-16
About

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.

Install

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.

  1. Create a Make API key

    Generate a key in your Make profile with the scenarios:read and scenarios:run scopes.

  2. 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.

  3. 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.

Connection

Endpoint and configuration

Endpoint
https://mcp.make.com/
Host
mcp.make.com
Transport
Streamable HTTP
Authentication
API key (MAKE_API_KEY) for local; OAuth on the hosted endpoint
Server name
make
Listing type
Official provider listing

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.

Verification

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.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that make appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: List the scenarios available to an assistant. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

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.

Provider page available on Oct 31, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

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.
Safety

Before you connect

Remote means provider access
  • 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.
Review path

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.

Reference

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