MCP Server | Bearnie

The Bearnie MCP server connects your AI assistant directly to the component registry. Ask for components in plain language and they get added to your project automatically.

Model Context Protocol is an open standard supported by Claude, Cursor, VS Code, and other AI tools.

Setup

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "bearnie": {
      "command": "npx",
      "args": ["@bearnie/mcp"]
    }
  }
}

Restart Cursor to load the server
Ask: "Add the dialog and button components from Bearnie"

Add to .mcp.json in your project:

{
  "mcpServers": {
    "bearnie": {
      "command": "npx",
      "args": ["@bearnie/mcp"]
    }
  }
}

Restart Claude Code, run /mcp to verify
Ask: "Add the dialog and button components from Bearnie"

Add to .vscode/mcp.json in your project:

{
  "servers": {
    "bearnie": {
      "command": "npx",
      "args": ["@bearnie/mcp"]
    }
  }
}

Click Start next to bearnie in the MCP panel
Ask Copilot: "Add the dialog component from Bearnie"

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "bearnie": {
      "command": "npx",
      "args": ["@bearnie/mcp"]
    }
  }
}

macOS: ~/Library/Application Support/Claude/
Windows: %APPDATA%\Claude\
Restart Claude Desktop after saving

Add to ~/.codex/config.toml:

[mcp_servers.bearnie]
command = "npx"
args = ["@bearnie/mcp"]

Restart Codex to load the server
Ask: "Add the dialog and button components from Bearnie"

Add to .opencode/mcp.json in your project:

{
  "mcpServers": {
    "bearnie": {
      "command": "npx",
      "args": ["@bearnie/mcp"]
    }
  }
}

Restart OpenCode to load the server
Ask: "Add the dialog and button components from Bearnie"

What your AI can do

Tool	What it does
`list_components`	Show all available components by category
`search_components`	Find components by name or description
`get_component`	View source code and dependencies
`add_component`	Add component files to your project
`add_components`	Add multiple components with dependency resolution (barrel last)

Components go to src/components/bearnie/, utilities to src/utils/, and theme styles to src/styles/.

For named imports from a single path, ask your assistant to add the barrel component after other components are installed.

For interactive components, the MCP flow also adds shared runtime files to src/utils/runtime/ so behavior works out of the box with no extra setup.

If a component needs an npm package, you’ll be told what to install.

Example prompts

“What form components does Bearnie have?”
“Add the tabs and accordion components”
“Add the tabs, accordion, and barrel components”
“Show me how the dialog component works”
“Build a settings page with cards and switches”

Environment

Variable	Default
`BEARNIE_REGISTRY_URL`	`https://bearnie.dev/registry`
`BEARNIE_REGISTRY_PATH`	Local registry path for development