3 min
Native Bloom MCP: block previews in chat, installs from a link
In Cursor every result comes back as a GIF. In Claude Code and Codex it is a video widget. Either way, I pick a block by watching it move.
Picking a block should not mean leaving the chat you are already building in. With the Native Bloom MCP server connected, the catalog search lives right in that chat. In Cursor it renders a GIF of each block, so you literally see every result moving next to your prompt. In Claude Code and Codex it renders video widgets, which gives you a good overview of the results so you can pick what you like.
A React Native MCP search that reads hidden metadata
The site's own search matches titles. The MCP search reads your whole sentence, turns it into real catalog filters, and ranks what comes back using metadata you never see on a block page. Synonyms and typos are handled, so spelling never costs you a search. I think it is really good: well organized, with strong ranking, and built around one goal. The output should show you what you actually need, not everything that happens to share a word with your query.
It works best when you ask for a part, not a product:
- Describe one thing. "a shader background animation" becomes filters on its own. "a carousel in Demos" narrows the search to the Demos collection.
- Use time words. "headers added this week" picks a window instead of searching for the word week.
- Skip the whole app. "build me a crypto app" gives the agent nothing to match. Find the parts first, then say what to build.
On a free account you get 25 searches a day, and results are preview-only: a title, a clip, and a link. Pro removes the limit.
A pasted block link is enough to install
This is the cool part. Add the GitHub MCP and Argent from Software Mansion next to Native Bloom. Then copy the link to any block in the catalog, paste it into the chat, and say "install this block". The agent does the job right away. You can grab a coffee and get on with your stuff.
Each server has its own job in that run. Native Bloom hands the agent the block's components, animations, packages, documentation, and source links. The GitHub MCP server lets it read the repo those links point to, instead of guessing the code from a video.
Argent closes the loop. It gives the agent direct control of the iOS Simulator and Android emulator: build and launch the app, inspect the component tree, tap through the screen, take screenshots, and read logs. So the agent sees the block running in your app before it calls the work done, which is what makes the result fast and reliable rather than a hopeful diff.
It needs the block's source to be reachable. A block from a paid kit has no public repo for the agent to read, and on a free plan the full block context comes only on spotlight blocks.
Add one URL, then paste a link
Setup is a single server URL and a one-time sign-in with your Native Bloom account. No API key, and nothing running on your machine. The config and the sign-in flow are on the MCP install page, so add it once and the next block you like is one pasted link away.