They say it's the USB-C for APIs to LLMs
Will there be an MCP Block soon?
Curious
1 Like
Hey @mascaritas - we probably won't build an MCP block, but we will be allowing AI queries to consume MCP Server tools, and they potentially exposing Retool Resources (or other data primitives) as MCP servers for consumption in other MCP clients (for example, in Claude).
Curious what you're looking to build with MCP + Retool?
2 Likes
This is great news. Thanks for your reply.
What I was imagining would be a block that can write queries to an api based on natural language input, very much like you have it already in the built in the "edit app" environment
If this block had some kind of memory or vector storage. and also remembered the error messages and which queries run through and which not, it would self learn how to communicate. with an api and would speed up the process imensly since user coud use "fuzzy queries"
I hope you get the idea of this use case. Curious to know what you think about it. Maybe there's even something that was already built that goes in this direction.
Actually, I imagine the MCP to be something like this, like an API on top of an API that can be queried in natural language.
Any outlook on which self-hosted stable version the AI Actions will include MCP capabilities?
Our use-case would revolve around enabling users to query a database through natural language
- Another AI Action should be summarizing the data.
- The query output should also be available for the user to download
1 Like
No promises, @seppi, but I anticipate our Q3 2025 release will contain beta versions of the various AI tooling that we're currently building out. 
2 Likes
Hey everyone,
there we are and able to integrate MCP meanwhile.
I did run into a situation where I am not understanding if Agent is able to use as an example firecrawl MCP in a smart way, any hints appreciated:
Hey everyone! @mascaritas @seppi Really exciting news, we're officially launching the Beta for Retool's MCP Server! 
We would love for you to be among the first to try it out. Sign up here to get access!
1 Like
Great News, this will support us respectively our tool of choice to come up with new functionality or improve upon existing apps I suppose.
1 Like
Wonderful @mascaritas can't wait to see what you build! 
Great to see the MCP server live. The read-focused scope makes sense as a starting point.
The use case we keep running into is less about one agent querying Retool and more about multiple agents that each need to interact with Retool as part of a larger workflow. For example one agent triaging inbound requests, another pulling data from Retool resources, and a third updating tickets based on the results. The individual Retool MCP connection works fine for each agent but the coordination between them is still something you have to build yourself.
We have been trying a few tools for that coordination layer. n8n for routing, teamoffsite.ai for the shared context and handoff between agents, and some manual webhook setups. Each handles a different part. Not settled on the right approach yet.
Curious whether anyone here is running multi-agent workflows that connect to Retool MCP and how you are handling the coordination between them.
1 Like