Build apps via MCP

📣 Retool Announcements 💥 Product Updates
,
1

App building with the MCP server is available in cloud instances. It will be available in upcoming stable and edge releases.

Builders on cloud instances can now use Retool's MCP server to build apps. Apps are built using React and use Retool's updated app builder. Connect the MCP server to Claude, ChatGPT, Codex, Cursor, Kiro, or another agentic coding environment, and describe the app you want to build. Retool's building agent generates the app and returns a preview link. Publish and manage the app from the app builder.

Beyond initial generation, you can also use the MCP server to:

  • Continue building or iterating on an existing app.
  • Monitor active builds and view past agent activity.
  • Review function runs that require human approval.
  • Inspect or read the files of an existing app.
  • Cancel a failed or in-progress build.

App building tools require the user to be a builder, and the builder must authorize the mcp:write scope. Refer to the tools reference for the full list.

Using the MCP server to build classic apps is not supported.

3

Since the mcp update to add this execute_resource_ts doesnt seem to be appearing in the list of tools.

4

I see that you've posted in a few different places, @Dominic_Stewart - thanks for reaching out! I just tested and confirmed that there seems to be a regression here. I'll dig into it and give you an update as soon as I can. :+1:

5

Hi Retool team,

I'm using the Retool MCP connector via Claude and ran into an authentication issue that seems specific to the React app file endpoints.

What works:

  • retool_list_apps and retool_get_app return data correctly, so the base MCP token is valid.

What fails:

  • retool_list_react_app_files (and presumably retool_read_react_app_files) returns:
401: {"success":false,"message":"Authentication failure. Missing access token","triggerOauth2SSOLoginAutomatically":false,"triggerSamlLoginAutomatically":false}

The failing endpoint is GET /api/ai/rr/git/v2/apps/{appId}/files.

Context:

  • Our org does not have SSO enabled.

  • App tested: NEW - Marketing Analytics Dashboard (ID 7135cbd6-5ba9-11f1-ae9c-ebc8e93e2aec), a React app.

  • I've already tried disconnecting and reconnecting the MCP connector — the basic tools still work, but the React app file endpoints continue to 401.

Ask:

  • Why do the /api/ai/rr/git/v2/... endpoints require a separate access token from the rest of the MCP, even without SSO?

  • Is there something we need to configure on the org / connector side to grant the MCP access to React app files, or is this a gap in the connector itself?

Happy to provide logs or test against a specific app if it helps.

Thanks!

6

I see the same thing, @Juan_Guerrero7 - thanks for flagging! And welcome to the community. :slightly_smiling_face:

I'll do some digging and get back to you with an update as soon as I can!

7

The completed app cannot generate public links, correct?

8

What’s the expected workflow for release management with this paradigm? In the classic app builder, we used the release version functionality. If we were building this locally using React we’d use git with CI/CD pipelines. How do we manage versions here?

9

@Tiffany_Yu - that's correct, at least for the time being. The ability to generate and share public links is something we'll be rolling out after launch!

@JaredStufft - it's actually very similar! You're prompted to create a new tagged release every time you publish app changes and then have the ability to set any specific release as the live version.

image
image842×608 36.6 KB

1 Like
10

Hi @Darren is the issue I reported above fixed now?

11

Not quite yet, @Juan_Guerrero7! The fix is scheduled to go out with our next release. :+1:

2 Likes