MCP

Your agent searches the catalog

One URL, no API key. Your coding agent finds a React Native block, then pulls the packages, docs, and source links it needs to build it.

Endpoint
https://mcp.nativebloom.dev/mcp

Works with Cursor, Claude Code, Codex, and any MCP client.

What it does

Ask, watch, build

The catalog's own search matches titles. The MCP server reads your sentence, turns it into real filters, and ranks what comes back.

Ask

Plain English in

“animated bottom sheet with blur” becomes real catalog filters. Synonyms and typos are handled — spelling never costs a search.

Watch

Clips play in chat

Every block comes back as a link plus a looping video, so you judge the motion before you touch a repo.

Build

Real source, not guesses

Pick a block and your agent gets its components, animations, packages, documentation, and source links.

Install

Add it in under a minute

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.

~/.cursor/mcp.json
{
  "mcpServers": {
    "native-bloom": {
      "url": "https://mcp.nativebloom.dev/mcp"
    }
  }
}

Use a project's .cursor/mcp.json instead to scope it to one repo.

Sign in once

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.

Free to try

Free accounts get 25 searches a day. Results are preview-only: a title, a clip, and a link. Pro is unlimited.

Tools

Four tools

Your agent picks these on its own. Knowing what they do tells you what to ask for.

  • search_blocksOne need, in plain English. Returns ranked blocks with previews, plus the terms to browse next.
  • search_blocks_batchA whole screen or flow at once. One labelled search per part, and no block repeats across them.
  • get_blockThe context to work with one block: learn how it works, experiment, and integrate it.
  • list_catalog_termsThe terms under a category, with how many blocks each has.
Usage

Getting good answers

The catalog is organised by part, not by screen. Once you know that, and the five words below, you can aim every search.

The words it uses

Block
One component or animation, with a video of it running and a link back to where the code lives.
Link
A block's page on nativebloom.dev. This is the thing you copy and paste back to your agent.
Category
The five kinds of term: components, animations, collections, packages, and authors.
Term
A single filter value, such as Bottom sheet, Scroll-driven, or react-native-effects.
Within
Searching inside one term, the way “a carousel in Demos” narrows to the Demos collection.

Ask like this

  • “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.

Not like this

  • “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.

Plans

Free to try, Pro to ship

The MCP server uses the same account and the same plan as the website. Nothing separate to buy.

Free

Enough to see whether it fits your workflow

  • 25 searches a day, reset at 00:00 UTC
  • Every tool, including batch search
  • Video previews on every block
  • Full context on spotlight blocks

Pro

For building with an agent every day

  • Unlimited searches
  • Every tool on the server
  • Video previews on every block
  • Full context for all open-source blocks