Execute_resource_ts tool missing from retool mcp server

  1. My goal: Use the Retool MCP server to execute queries against resources
  2. Issue: execute_resource_ts is not available as a tool
  3. Steps I've taken to troubleshoot: Checked docs, disconnected mcp, reconnected, reauthorized, restarted Claude Code and Claude Cowork
  4. Additional info: (Cloud or Self-hosted, Screenshots): Cloud

A few things:

  1. Tried yesterday before ya’ll added the app builder tools to the MCP server. The docs still said the tool was execute_resource_typescript, but the returned tool from the MCP server was execute_resource_ts

  2. When Claude ran the tool, got an error: POST /api/resources/typescript/execute
    500 {"apiError":"internal_server_error","message":"Internal server error"}

  3. Waited 12 hours, and tried again

  4. Saw you released the app builder tools and updated docs with the correct tool names. Docs now correctly show the tool as execute_resource_ts, same as what was returned yesterday (even if the tool didnt work)

  5. However, execute_resource_ts now doesnt exist as a tool returned by the Retool MCP server.

I’ve tried on Claude Code (CLI) and Desktop App, and on the web. I’ve restarted the agents, disconnected, reconnected, reauthorized. I’m an admin on our domain, and we’re running Retool in the Cloud, on the Team plan.

Anyone else seeing this?

Yeah I have a similar problem. I had built a lot of infrastructure around the MCPs ability to read the database but changes yesterday have meant this isn’t working now.

Is there a reason for this change? Will the MCPs functionality be restored?

I'm currently looking into this, but am also seeing a regression here. I'll report back with more info as soon as I can. :+1:

1 Like

We've identified the root of the issue and will be shipping a fix later today!

Did it make it out? I dont see the fix yet.

Apologies, @Dominic_Stewart! It looks like it didn't go out after all. I'll reconvene with the owning team to get you an updated timeline. :folded_hands:

Sounds good, its blocking my work from using Retool in my AI flows. So anything we can do to get a fix out ASAP would be good.

1 Like

You should be back in business, @Dominic_Stewart! I just verified on version 4.3.0.