6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Run Make scenarios and manage your Make account from an AI assistant.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Make MCP server connects Make to Claude, ChatGPT and any MCP-compatible agent. It exposes 67 tools that manage scenarios, connections, data stores, webhooks, teams and organizations, and it turns your own active scenarios into callable tools. Sign-in is OAuth. Running scenarios works on every plan; management needs a paid one.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
scenarios_run executes an automation you built, and that automation can reach every app you have connected to Make. Sending mail, writing to a CRM, moving money through a payments integration — all of it sits behind one generic-looking tool name. This is a materially larger blast radius than a connector that only touches its own vendor's data, and Make's documentation does not describe a confirmation step before a run.scenarios_activate re-arms a schedule. Activating a scenario is not a one-shot action; the scenario may then run on its own afterwards. Make requires scenarios to be active before they are discoverable as tools, so activation is part of the normal flow rather than an edge case.429/IM310 and refuses the run — the same pause that stops your scheduled automations. Make also documents that the run endpoint is exempt from the organization request limits, so those are no brake.https://mcp.make.com/.well-known/oauth-protected-resource returned HTTP 200 on 2026-08-18 with resource, authorization_servers and bearer_methods_supported and no scopes_supported field. The authorization server's own metadata returned HTTP 200 and also omits scopes_supported. We therefore cannot state a machine-readable scope list. The three consent options named above come from Make's documentation, not from a wire observation.Two different things. It runs your Make scenarios as callable tools, and it manages your Make account through 67 tools covering scenarios, connections, data stores, webhooks, teams and organizations. Make's documentation describes it as letting clients run scenarios, check data stores, or invite members to an organization.
Any plan runs scenarios; management needs a paid plan. Make's help centre states that users on all plans can use scenario run scopes, and those on paid plans can use management scopes. So a Free account connects and triggers scenarios, but the 67 account-management tools stay unavailable until you upgrade.
Yes. A scenario run through the connector is a real run and consumes operations exactly as any other run does. Make's scenarios API states the run is refused with a 429 and code IM310 when the organization or team is paused for exceeding an operations or data transfer limit, the same way Make stops scheduling.
Because that is the endpoint Make publishes. The OAuth connection URL is the bare host, and appending the conventional /mcp path returns HTTP 404. We probed both on 2026-08-18: the bare host answers with a 401 authentication challenge, which is the correct endpoint asking you to sign in.
Only scenarios that are active and scheduled on demand. Make's help centre lists both conditions as requirements for a scenario to be discoverable by MCP clients. You also need scenario inputs and outputs configured, plus a scenario description, which is what the assistant reads to decide when to call it.
Only on the MCP token connection, not on OAuth. Make documents organizationId, teamId and scenarioId query parameters that narrow which scenarios become tools, and states the levels are mutually exclusive. OAuth lets you pick one organization at consent, and Make notes a Teams plan or higher allows team-scoped user accounts.
25 seconds for a scenario run over OAuth, and 30 seconds for a management tool. Make documents that a timed-out scenario keeps running for up to 40 minutes and returns an executionId you can use to fetch the result later. Token-based connections get longer limits, up to 5 minutes 20 seconds.
https://mcp.make.com — an anonymous initialize returns/mcp-server/make-mcp-server form 307s here, so the short URL is the canonical one). Source for the connection URLs, transports, timeout limits, the 40-minute continuation, the maxToolNameLength parameter, the plan gate and Make Skills. · retrieved 2026-08-18IM310 operations-limit refusal and the rate-limit exemption. · retrieved 2026-08-18developers.make.com/robots.txt allows crawling and carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — synthesis into AI-generated output is expressly permitted by the publisher. · retrieved 2026-08-18www.make.com/robots.txt allows the path, so this is bot-blocking rather than a policy signal, and we did not read the page) · retrieved 2026-08-18Connect Make once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.