retool_get_resource_ts_definitions and retool_execute_resource_ts work fine for database resources, but I'm unable to use them for REST API resources defined in Retool.
retool_get_resource_ts_definitions returns a 404 for REST API resources. with a response…
{ "apiError": "not_found", "message": "Resources not found or unsupported in environment "production": b2d91442-8a0c-4fad-90bb-bc303dd3984b" }
My company doesn't actually use databases directly from retool. Instead we have everything connected via admin endpoints exposed in our own application. Pretty much everything we do, pretty much all of our resources are REST API resources.
I couldn't find any configuration to allow the MCP to access a particular REST API either.
It may seem silly to use retool to call other APIs, but the truth is retool provides the query definitions in a convenient execution environment that we're already well familiar with, as well as an authentication layer, and an audit log, And a few other things, all wrapped up nicely for us, which makes it particularly convenient for us to call these APIs via retool from our agents, instead of directly.
Welcome to the community, @Jason_Stillwell! Thanks for reaching out and sharing some context about how you're currently using the MCP.
REST API resources definitely can be queried via MCP, but only if they have an OpenAPI spec attached. That is what really enables the agent to introspect and understand the available endpoints.
Most third-party platforms publish specs for their own APIs, but Claude/Cursor/Codex should be able to generate one for your own custom backend. Let me know if you have any questions!
Thanks, this worked great. I generated and openapi spec for my API and applied it to the API resource in retool, and I was able to call it just fine through the retool MCP server with an agent.
