Retool MCP server

What the model can do

Retool organisation admin: users and pending invites, permission groups with their members and access levels, apps, workflows with their schedules, workflow runs, human-in-the-loop user tasks, resources (data sources) and usage. When you ask, can invite or create a user, revoke an invite, disable a user, create or delete a group, add people to a group or remove them, submit, reassign or cancel a user task, create a folder, and delete an app or a workflow.

Reads

• retool_list_usersRetool users: id, name, work email, active or disabled, admin, user and seat type, and when added.
• retool_list_groupsRetool permission groups: id, name, members (id, email, group admin), and the group's access to all apps, resources, workflows and the query library.
• retool_list_appsRetool apps: id, name, description, classic or React, folder, whether a module or mobile app, protected or synced with source control, published URL…
• retool_list_workflowsRetool workflows: id, name, description, schedule (cron and timezone), enabled or not, folder, protected, the group it runs as, and when last changed.
• retool_get_workflow_runOne Retool workflow run by id: status, workflow, what triggered it and when, and any user tasks it is waiting on (without their context or output).
• retool_list_user_tasksRetool workflow user tasks (human-in-the-loop approvals): task name, status (pending, submitted, cancelled, expired), workflow and run, assignees…
• retool_list_resourcesRetool resources (the databases and APIs apps query): id, type, name, folder, whether protected or data-access enforced, and when changed.
• retool_usage_summaryRetool usage for a date range (at most about 30 days from the start): page views and saves, active users and trailing-30-day users…

Acts, when you ask

These change something in Retool. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• retool_invite_userInvites a person by email to the Retool organisation, optionally straight into groups and onto a named seat.
• retool_create_userCreates an active user in the Retool organisation with the email and name given, who can then sign in; may take a paid seat.
• retool_delete_user_inviteRevokes a pending Retool invite so its link no longer works.
• retool_disable_userDisables a Retool user, so they can no longer sign in or use any app.
• retool_create_groupCreates a Retool permission group, optionally with access to all apps, resources or workflows (none, use, edit or own).
• retool_delete_groupDeletes a Retool permission group; its members lose whatever access the group gave them.
• retool_add_group_membersAdds Retool users to a permission group, giving them its access; as_group_admin also lets them manage the group.
• retool_remove_group_memberRemoves a user from a Retool permission group; they lose the access it gave them.
• retool_submit_user_taskSubmits a pending Retool user task with the output the workflow expects, recorded as submitted by the email given…
• retool_reassign_user_taskReassigns a Retool user task to the users and groups given, replacing who it waits on; recorded as done by the email given.
• retool_cancel_user_taskCancels a pending Retool user task, recorded as done by the email given; the workflow carries on down its cancelled path.
• retool_create_folderCreates a Retool folder for apps, workflows, resources or agents, optionally inside another folder.
• retool_delete_appDeletes a Retool app; everyone who uses it loses it.
• retool_delete_workflowPermanently deletes a Retool workflow and its run results; it does not go to Trash and cannot be undone…

Connect it

First connect Retool on Dashboard → Connections, then add Memtro to your client once. The Retool tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Retool connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which user tasks are waiting for approval?
• › Who has admin access in Retool?
• › Which workflows run on a schedule?
• › How many active users did we have last month?
• › Who is in the Finance group?

Questions

Is this an official Retool MCP server?

No. It is Memtro's MCP server with Memtro's Retool connector behind it: the connector reads Retool through its API with the credentials you connect on Dashboard → Connections, and Retool publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Retool?

Only when you ask, and only what it has been granted: invite a person to the Retool organisation, optionally into groups (uses a seat once claimed); create a Retool user; revoke a pending invite; disable a user so they can no longer sign in; create a permission group; delete a permission group; add users to a group, or make them group admins; remove a user from a group; submit a workflow's user task (the workflow resumes); reassign a user task to other users or groups; cancel a user task; create a folder; delete an app; permanently delete a workflow. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server