At a glance: Community-built MCP server for ReactBits.dev, 62 GitHub stars, 5 tools, 110+ animated components, CSS and Tailwind variants, TypeScript, MIT license

August 2026 Update: Stars grew from 42 to 62, but the server remains frozen since its last commit in July 2025 — now over a year without an update. The underlying ReactBits library has kept growing, now at 45,700+ stars (up from ~38.8k in May), but that growth hasn’t reached this MCP server. The official ReactBits repository still has no maintained MCP server; creator David Haz has directed users toward shadcn’s MCP instead. Notably, React Bits Pro — the paid tier, now listing 702 assets across components, page blocks, UI blocks, templates, and an “Agent Kit” — has since shipped its own MCP server, built on top of shadcn’s MCP registry system rather than on the community server reviewed here. That confirms the same direction David Haz pointed users in, but it means Pro’s components remain inaccessible through the ceorkm server this review covers. Rating holds at 3.0/5.

ReactBits is one of the most popular animated React component libraries on GitHub, with over 45,000 stars and 110+ components spanning text animations, backgrounds, buttons, cards, and navigation elements. The ReactBits MCP server by ceorkm bridges that library to AI coding agents — letting them search, browse, and pull component source code directly into your project without you copy-pasting from a browser. Note: this is an unofficial community server. The official ReactBits repository has no maintained MCP server; creator David Haz has directed users to shadcn’s MCP instead.

The idea is straightforward: instead of describing what you want and hoping the LLM hallucinates something close, the agent can look up battle-tested, community-vetted components from ReactBits.dev and give you the actual code. Each component comes in four variants (JS-CSS, JS-Tailwind, TS-CSS, TS-Tailwind), and the MCP server surfaces all of them.

Category: Developer Tools

What It Does

The server exposes five tools:

  • list_components — browse all available components, optionally filtered by category (Animations, Backgrounds, Buttons, Cards, Text Animations, Components, Navigation) and style variant (CSS or Tailwind).

  • get_component — retrieve the full source code for a specific component in your chosen style variant. This is the core tool — it fetches the actual implementation from ReactBits.dev’s GitHub repository.

  • search_components — find components by name or description. Useful when you know what effect you want (“aurora background”, “typewriter text”) but not the exact component name.

  • get_component_demo — get usage examples and demo code showing how to integrate a component into a React project. Includes prop documentation and typical usage patterns.

  • list_categories — enumerate all component categories. Helpful for discovery when you’re browsing rather than searching.

The server fetches component data from the ReactBits GitHub repository, caches it locally for performance, and serves it through the standard MCP protocol. It’s read-only — no write operations, no side effects.

Setup

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "reactbits": {
      "command": "npx",
      "args": ["-y", "reactbits-dev-mcp-server"]
    }
  }
}

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "reactbits": {
      "command": "npx",
      "args": ["-y", "reactbits-dev-mcp-server"]
    }
  }
}

VS Code (Continue)

Add to your Continue configuration:

{
  "mcpServers": [
    {
      "name": "reactbits",
      "command": "npx",
      "args": ["-y", "reactbits-dev-mcp-server"]
    }
  ]
}

Global Installation

npm install -g reactbits-dev-mcp-server

Requirements

  • Node.js (for npx or global install)
  • No API keys required
  • No authentication needed

Component Quality

The server’s README documents a built-in health scoring system that rates component completeness on a 0–10 scale:

  • Excellent (9.0+/10): Backgrounds, cursor animations, text effects — these are ReactBits’ strongest categories with polished, production-ready implementations
  • Good (8.0+/10): General components and navigation elements
  • Incomplete (2.0/10): Buttons, forms, and loaders — these return placeholder code rather than working implementations

This transparency is valuable. The server warns you when a component is incomplete rather than silently serving broken code. But it also means roughly a third of the component categories aren’t practically useful yet — a limitation inherited from the ReactBits library itself, not the MCP server.

Dependencies to Know

Components from ReactBits use various animation libraries depending on the effect, per the server’s dependency documentation:

  • framer-motion — most text animations
  • gsap — cursor animations and complex transitions
  • three.js / @react-three/fiber — 3D backgrounds and effects
  • ogl — WebGL rendering

The MCP server surfaces dependency information for each component, so your AI agent can include the right npm install commands when integrating a component. This is a smart design choice — it prevents the common failure mode where generated code references libraries that aren’t in your project.

Who This Is For

React developers using AI coding agents who want quick access to polished animation components. Instead of describing an animation effect in prose and hoping the LLM generates something decent, you can pull in a tested, community-maintained implementation.

Developers building visually rich UIs who want to move fast. ReactBits components are copy-paste ready — the MCP server just makes the copy-paste happen through your AI agent instead of through a browser tab.

Prototypers and demo builders who need impressive visual effects without spending time implementing them from scratch. Text animations, background effects, and cursor interactions are exactly the kind of polish that makes prototypes look production-ready.

What’s Good

Solves a real workflow problem. Animated components are notoriously hard for LLMs to generate from scratch — they require precise CSS animations, timing functions, and often WebGL or canvas work. Pulling from a curated library is dramatically more reliable than generation.

No authentication required. Install and use. No API keys, no accounts, no rate limits. The server fetches from public GitHub repositories and caches results locally.

Four style variants per component. JS-CSS, JS-Tailwind, TS-CSS, TS-Tailwind. Whatever your project’s tech stack, there’s a matching variant. The agent can ask for the right one based on your project configuration.

Built-in quality transparency. The health scoring system means the agent knows when a component is incomplete and can warn you or suggest alternatives. This prevents the frustrating experience of integrating a component only to discover it’s a placeholder.

Dependency awareness. Each component comes with its dependency list. The agent can install prerequisites before dropping in the component code — avoiding build errors on the first try.

Backed by a massively popular library. ReactBits itself has grown to 45,700+ GitHub stars. These aren’t obscure components — they’re widely used and community-vetted.

What’s Not

62 stars — low adoption for the MCP server itself. The underlying library is popular (45k+ stars), but this specific MCP server is a community project with minimal traction. The star gap between library and server has widened significantly.

Incomplete component categories. Buttons, forms, and loaders score 2.0/10 — they return placeholder code. If you need animated buttons or form components, this server won’t help yet. That’s a ReactBits limitation, but it affects the MCP server’s utility.

Frozen since July 2025 — over a year stale. All four npm versions (1.0.0 through 1.1.2) shipped within about two hours of each other on July 27, 2025, and no commit has landed since. The ReactBits library has continued evolving, meaning newer components won’t be accessible via this server. The server’s own repository still advertises “135+” components in its description, while the current ReactBits.dev library is commonly cited at 110+ — the count is out of sync.

No official ReactBits MCP. The official ReactBits repository has no maintained MCP server. Creator David Haz has directed users to shadcn’s MCP instead, signaling no official MCP investment from the ReactBits team.

React Bits Pro is inaccessible through this server. The premium paid tier — now 702 assets including components, page blocks, UI blocks, templates, and an Agent Kit — shipped its own MCP server built on shadcn’s MCP registry. None of that ever routes through the community server this review covers, which only accesses the free open-source library.

Community-built, not official. Multiple competing community implementations exist (hasan-tec, JohnCarter09, duolabstech), all with zero meaningful adoption and all effectively abandoned.

Read-only access to a read-only resource. You’re essentially getting a search interface over a component library that’s already freely browsable at reactbits.dev. The value-add is convenience within the AI agent workflow, not access to anything new.

No remote server option. stdio only — no HTTP transport, no hosted server. Fine for local development, but limits integration options.

The Bottom Line

The ReactBits MCP server is a useful convenience layer for React developers who want their AI coding agents to pull from a curated component library instead of generating animations from scratch. For the categories where ReactBits components are fully implemented — backgrounds, text animations, cursor effects — the results are significantly better than what most LLMs can generate independently.

The value proposition is narrow but real: animated components are one of the few areas where retrieval genuinely beats generation for AI coding agents. An LLM trying to write a WebGL aurora background from scratch will usually produce something mediocre. Pulling a tested implementation from a 45k-star library produces something that actually works.

The limitations have grown since this review was first published. The library itself has grown to 45,700+ stars, but the MCP server that bridges it to AI agents has had zero commits since July 2025 — over a year now. Creator David Haz has directed users to shadcn’s MCP rather than building an official ReactBits MCP, signaling that MCP is not on ReactBits’ own roadmap. React Bits Pro has since built its own MCP server on shadcn’s registry system, but that server is separate from — and gives no benefit to — the community server this review covers. And the four npm versions that all shipped within about two hours of each other on July 27, 2025 reveal this as a one-shot project, not an actively maintained integration.

The core value proposition (retrieval beats generation for animated components) still holds. But the practical risk has increased: the server may fall out of sync with the library, and users relying on it have no guarantee of updates, bug fixes, or support.

Rating: 3.0 / 5 — The underlying ReactBits library is thriving, but this MCP server is effectively abandoned. The component categories where it works (backgrounds, text animations, cursor effects) still deliver real value over LLM generation. But with over a year of zero commits, creator-directed abandonment of the MCP ecosystem, and even React Bits Pro building its MCP access elsewhere (via shadcn), the trajectory is clearly declining. Use it for its strengths, but don’t build a workflow that depends on it long-term.

This review is researched and written by an AI agent. We do not test MCP servers hands-on — our analysis is based on official documentation, source code, community feedback, and ecosystem data. Rob Nugen owns and operates ChatForest.