General availability of Retool's MCP server: what changes

What Retool shipped on November 11, 2026

Retool made its MCP server generally available on November 11, 2026, for cloud and self-hosted instances on version 4.86 or later, and the changelog lists it on all plans (changelog entry). For a small B2B team, the change is about who can reach Retool from an AI agent such as Claude Code, ChatGPT Cowork, or Cursor, and none of the vendor pages we opened state a price change for that access.

An MCP server, in plain terms, is an endpoint that lets an AI client call a product's tools under the permissions of the person who signed in. This is an access decision, not a new app-builder purchase, so the questions that matter are about roles, plans, and approvals more than features.

GA version floor: 4.86 or later according to Retool (2026) is the first gate: any self-hosted instance below that version falls outside the launch.

TL;DR: The server is generally available and on all plans, but agent access controls appear only on higher tiers, so check your plan and self-hosted version before anyone connects an agent to an admin account.

Key Takeaways

• Retool's changelog dates general availability to November 11, 2026, for cloud and self-hosted instances on version 4.86 or later.

• The pricing page places agent access controls on Business and Enterprise, not on Team, so your tier decides how tightly agents are limited.

• Connections use HTTP transport and OAuth 2.0, and each user can grant only the scopes their Retool role allows.

• Zapier's MCP connects agents to a large app catalog and records each MCP action, so it solves a different problem from Retool's server.

• AI credits, not the connection itself, drive most cost questions, because app building draws on credits when you use Retool-managed keys.

• Act this month only if you can name your admins, an approval step for bulk changes, and the version on every self-hosted instance.

Signal vs speculation: what Retool has published

Published by the vendor (signal):

• The GA changelog entry names Claude Code, ChatGPT Cowork, and Cursor as example environments and lists these use cases: build and edit apps, import existing React apps, administer organization and users, manage permissions, explore and edit resources, and explore and investigate workflows (GA entry).

• The setup guide gives a cloud endpoint of mcp.retool.com, a self-hosted path of https:///mcp, HTTP transport, and OAuth 2.0 (setup guide).

• The beta history is dated. The first changelog entry, "MCP server for Retool," is dated April 23, 2026. It covers bulk-inviting users and managing pending invites, and it says app building is future work. A "Build apps via MCP" entry dated May 28, 2026 is tagged Beta (changelog tag page).

• The vendor's pages conflict on two points. Retool's launch post, dated May 8, 2026, says in its body that the server is "now available in public beta," while an undated update note at the top says it is "out of public beta and generally available" (launch post). The setup guide says self-hosted instances on "version 4.0.0 and later" qualify, while the GA entry sets 4.86. We treat the dated GA entry as the newer statement and recommend confirming the floor with Retool before rollout.

Not published by the vendor on the pages reviewed:

• Rate limits and usage caps: the vendor has not published this.

• Regional availability: the vendor has not published this.

• Run history or audit-log detail for the Retool server: the vendor has not published this. The launch post's update note says admins can monitor MCP token spend in the AI monitoring dashboard, which is the nearest published control.

• Hourly agent rates: the vendor has not published this on its pricing page.

Our analysis (speculation, not vendor claims):

• We expect the tier question, not the connection itself, to decide what a small team pays for control.

• A team with one admin may gain little beyond faster permission reviews, while a team with several builders will reach its AI-credit allowance sooner. This is our reading of the published allowances, not a measured outcome.

How we evaluated these options

We compared Retool's generally available server with its own beta, because a team already on Retool would have used the beta. We also compared it with Zapier's MCP product, the common alternative for teams that automate across SaaS apps. We weighted six criteria by what a small B2B buyer must decide this month, drawing only on vendor pages and two independent sources. The weights total 100 percent and are our judgment, not a published scoring method. We did not run either product.

The weights reflect this reader's decisions. A team with no Retool footprint should drop the Retool-specific rows and weigh the rest again.

What changed from the beta

The beta began with organization and user tools. App building arrived later as a beta entry on May 28, 2026, and the GA entry adds importing existing React apps, a use case the beta entries we read do not mention. The vendor does not say when import was added. The most visible change is the label: the GA entry is the first dated statement that the server is generally available, and the May 8 blog update note makes the same claim without a date.

Market context points the same way. Stacklok's 2026 software report says nearly half of software companies use MCP in production, and its page gives the figure that matters most for a buyer: Broad production: 19% of software companies according to Stacklok (2026). The page does not state a sample size or field dates, so treat it as directional.

For another MCP launch explained in the same format, see iManage and Thomson Reuters MCP integration explained.

Pricing and what agent usage costs

Retool prices per user per month. Its Team and Business plans split seats into builders and internal users, and each plan carries a monthly allowance of AI credits. Its pricing page says annual billing saves 20 percent compared with monthly billing. Zapier prices by plan and task tier, and its MCP page says each tool call uses two tasks from the existing quota.

Team plan builder seat: $12 monthly or $10 yearly according to Retool (2026) is the entry price most small teams will see first.

Professional plan (750 tasks): $19.99 per month, billed yearly according to Zapier (2026) is Zapier's lowest paid tier, and its Enterprise tier is not published.

Pricing checked November 11, 2026.

Sources for the table: Retool pricing and Zapier pricing.

Illustrative only, not a customer and not a measured result: take a team of four builders and six internal users on Retool's Team plan. At monthly billing, that is 4 builders × $12 = $48 plus 6 internal users × $7 = $42, or $90 a month ($1,080 a year). At yearly billing, it is 4 × $10 = $40 plus 6 × $5 = $30, or $70 a month ($840 a year), so the difference is $240 a year before any other cost. The Team plan includes 1,000 AI credits a month on the plan, app-building requests draw on that allowance when Retool-managed keys are used, and admin and resource exploration draw none of it. Cloud connections point clients at mcp.retool.com, and each user authorizes only the scopes their role allows.

Zapier's per-task model scales faster than it looks, so the next table counts tool calls, not seats. It ignores other Zaps, which also use the quota.

Who should choose which option

Retool's MCP server

Who this is for: teams already running internal tools on Retool, with at least one admin who manages users and permissions by hand today and builders who want an agent to help edit apps.

Red flags: you do not run Retool in production, you need agent access controls but would stay on the Team plan, or you cannot confirm that each self-hosted instance runs version 4.86 or later.

Best fit: this server suits a team whose admin work already lives in Retool, because the GA use cases cover organization and user administration, permissions, resources, and workflows.

Limitations: the pricing page places agent access controls on Business and above. The pages we opened do not say whether the setup guide's scope model is the same thing, so ask Retool before relying on it. The vendor has not published rate limits, and its version statements conflict, as noted above.

Implementation: add the server URL with HTTP transport, complete the OAuth sign-in in the browser, select scopes, and authorize. You may need to restart the agent afterward. On Claude Team and Enterprise, an admin adds the server as a custom connector. VS Code needs version 1.102 or later with GitHub Copilot Chat, and Gemini Enterprise needs a Google Cloud admin with the Discovery Engine Editor role.

Evidence: GA entry, setup guide, pricing, and launch post.

Zapier's MCP

Who this is for: teams that already run Zaps and want AI clients to trigger them with a record of each action.

Red flags: your work sits inside Retool's apps and admin screens, you cannot budget for per-task use, or you need Enterprise pricing before you can decide, and that price is not published.

Best fit: Zapier suits a team whose agent must act across many SaaS apps rather than inside Retool, and its MCP page cites 9,000+ apps according to Zapier (2026).

Limitations: pricing is task-based, and each tool call uses two tasks. The Enterprise price is not published, and the pages we opened do not state a self-hosted option.

Implementation: IT can enable or disable MCP per workspace. Admins set app and action-level access controls, and users choose which apps and actions an agent may use. Credentials stay in Zapier's managed connection layer rather than passing into the model, and the page states SOC 2 Type II certification.

Evidence: Zapier MCP and Zapier pricing.

Build, buy, or stitch it together

There are three routes. Retool's server is buy-inside-Retool, Zapier's MCP is buy-across-apps, and the third route is to stitch a workflow together in Zapier, Make, or n8n, or to build it in-house. The stitched route is not weaker on paper: those tools can support run histories, retries, and error branches when configured. The buyer then designs and owns observability, idempotency (so a retried step does not create a second invitation), escalation paths, access controls, and maintenance.

US Tech Automations builds and runs custom automation workflows for businesses, starting with a process map and building the workflow on its own platform. Its homepage lists connections to Gmail, Google Calendar, Google Sheets, HubSpot, QuickBooks, Stripe, and more, and its sample support workflow includes an approval step: "You approve, edit or reject each draft before it sends." The homepage does not list a Retool connection and does not describe audit logs or access controls, so those are prerequisites to confirm before any scoping.

A proposed, configurable workflow for a quarterly access review would start on a scheduled trigger, such as the first business day of each quarter. It would pull a list of Retool users and roles through an export or API method that US Tech Automations would need to confirm before build, compare that list with the current staff roster in Google Sheets, and draft a list of accounts to keep, change, or remove. The output is a review sheet with one row per account, the proposed action, and the reason. Human review sits at the end: an admin approves each removal or role change before anything changes in Retool, and the workflow makes no change on its own. Prerequisites are a named admin, a written role map, and confirmed export access. The sheet is a spreadsheet record, not a platform audit trail, and no result has been measured.

A second proposed workflow covers a new hire. The trigger is a new row in an onboarding tab in Google Sheets, or a HubSpot deal reaching a "hired" stage, since HubSpot is named on the homepage. The workflow drafts the Retool invitation list and the role each person needs, then posts it to the hiring manager for approval. Bulk invitations are high-impact, and the launch post lists bulk-inviting users among the server's tools (launch post), so the invite step should wait for a written admin approval. The output is a draft invite list and a confirmation message. Prerequisites are a role map, the admin approval step, and a confirmed Retool connection.

When NOT to use a US Tech Automations build: skip a custom build if your need is a single Retool admin task done occasionally in Retool's own screens, because the native admin tools are simpler. Skip it if the only job is moving form responses into a sheet, where one Zapier zap is simpler and cheaper to run. Skip it if a developer already maintains an in-house script with logging and approvals, because a rebuild adds a second system to own. Teams still choosing between routes can start with our guide to free automation tools for small teams before committing budget.

Common mistakes to avoid

The OWASP MCP Top 10 gives a useful risk frame: OWASP's MCP Top 10 lists ten risk categories according to OWASP (2025). Two of those categories, privilege escalation through scope creep and lack of audit and telemetry, match the mistakes below. The project is in its beta phase and calls itself a living document, so treat it as a checklist rather than a standard.

• Reading "all plans" as "all agent controls." Agent access controls sit on Business and above according to the pricing page.

• Using the setup guide's self-hosted floor of 4.0.0 instead of the GA entry's 4.86.

• Letting an agent run bulk actions. Put an approval step in front of bulk invitations and any permission change.

• Forgetting AI credits. App building draws on them when you use Retool-managed keys.

• Counting one task per Zapier tool call. The MCP page says two.

• Giving the mcp:admin scope to builders by default. The setup guide limits it to admins.

Decision checklist for this month

• Every self-hosted instance runs version 4.86 or later.
• Your plan includes agent access controls, or you accept that it does not.
• Only named admins can hold mcp:admin.
• A written approval step covers bulk invites and permission changes.
• Monthly AI-credit use is estimated against your plan's allowance of 250, 1,000, 3,000, or 10,000 credits.
• Your AI clients are on the documented list, and a Claude admin has added the connector where required.
• Retool has confirmed in writing whether the setup guide's scopes count as agent access controls, and what run history exists.

Our recommendation: if the first four boxes are ticked, run a pilot with one admin and a small group of builders this month. If they are not, wait. A mistaken admin grant is harder to unwind than a one-month delay.

Frequently asked questions

Is Retool's MCP server generally available now?

Yes, the dated changelog entry of November 11, 2026, says it is generally available for cloud and self-hosted instances on version 4.86 or later. Older Retool pages still describe a beta, so confirm the status with Retool before you quote it internally.

Does the MCP server cost extra?

The changelog lists the server on all plans, and the pricing page does not list a separate MCP price. Your bill comes from seats and AI credits, and app building draws on those credits when you use Retool-managed keys.

Which AI tools can connect?

The GA entry names Claude Code, ChatGPT Cowork, and Cursor, and the setup guide documents more clients, including Claude, Codex, ChatGPT, Gemini CLI, Kiro CLI, and VS Code with GitHub Copilot Chat. Clients that are not on those pages are not covered by this review.

Do we need a developer to set it up?

The sign-in is browser-based and uses OAuth, so an admin with rights to authorize scopes can run it. Claude Team and Enterprise organizations need an admin to add the server as a custom connector, and VS Code needs version 1.102 or later.

Is Zapier's MCP a replacement for Retool's server?

No, because they connect agents to different things. Retool's server reaches your Retool apps, users, and resources, while Zapier's reaches the apps in its catalog, so one rarely replaces the other.

Should we switch tools this month?

Do not switch because of a launch alone. Pilot the Retool server only after the checklist passes, and treat it as an addition to your current process. For a different recent launch, see GPT-5.6 alternatives after the Astra launch.

Does this change what our admins can do in Retool?

The GA use cases include administering organizations and users, managing permissions, and exploring and editing resources, so an agent can perform those tasks through the connection. Each user can grant only the scopes their Retool role allows, so an agent's reach stays within what that user already has.

Bottom line for a small B2B team

Retool's MCP server is generally available as of November 11, 2026, on all plans, but the controls that limit agents sit on higher tiers, and the vendor's own pages still disagree on the beta history. Confirm your plan, your self-hosted version, and your approval steps first. If you want to see how a configured approval-gated access review would look in practice, see how US Tech Automations configures this.