Plain English in
“animated bottom sheet with blur” becomes real catalog filters. Synonyms and typos are handled — spelling never costs a search.
The catalog's own search matches titles. The MCP server reads your sentence, turns it into real filters, and ranks what comes back.
“animated bottom sheet with blur” becomes real catalog filters. Synonyms and typos are handled — spelling never costs a search.
Every block comes back as a link plus a looping video, so you judge the motion before you touch a repo.
Pick a block and your agent gets its components, animations, packages, documentation, and source links.
Point your client at one URL. There is no API key, no package to install, and nothing running on your machine.
Add the server to your global MCP config.
{
"mcpServers": {
"native-bloom": {
"url": "https://mcp.nativebloom.dev/mcp"
}
}
}Use a project's .cursor/mcp.json instead to scope it to one repo.
Your client shows a Connect button the first time it calls the server. Sign in with your Native Bloom account in the browser, and results follow your plan from then on.
Your agent picks these on its own. Knowing what they do tells you what to ask for.
The catalog is organised by part, not by screen. Once you know that, and the five words below, you can aim every search.
“use native bloom to find tab bar”
One part, described by how it looks and moves.
“a shader background animation”
Plain English. The words become filters on their own.
“a carousel in Demos”
Names a term to search inside when you already know it.
“headers added this week”
Time words choose a window instead of being searched for.
“build me a crypto app”
Don't hand the agent a whole product. Find the parts, pick a block, then say what to build.
“find me something nice for my app”
Nothing searchable in it. You get guidance back, not blocks.
The MCP server uses the same account and the same plan as the website. Nothing separate to buy.
Enough to see whether it fits your workflow
For building with an agent every day