Chakra UI MCP (official)

95/100
Last tested 2026-11-11 (Fresh: tested within 30 days) Working (tool call tested 2026-11-11) No key needed for the tools we called

No advisories in range for tested 2.1.1 (checked 2026-11-11)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs10/15
  • License10/10

Tested npm @chakra-ui/react-mcp 2.1.1 (MIT; repo chakra-ui/chakra-ui apps/mcp, 40,723 GitHub stars when checked; npm package last published 2025-11-03). Stdio, 7 read-only tools for Chakra UI v3 components, examples, theme tokens and v2-to-v3 migration, no account. Real calls: list_components, get_component_props for button and get_component_example for dialog all returned content. customize_theme and v2_to_v3_code_review were not called.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 3 of 3 read calls passed, no key. Evidence: local test run, Nov 11, 2026.

Transport (tested 2026-11-11): stdio

Token cost (estimate): approx. 1561 tokens, cl100k estimate (7 tools, measured 2026-11-11, version 2.1.1). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 4 read, 0 write (state-changing), 3 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • customize_theme — unclassified
  • get_component_example — read
  • get_component_props — read
  • get_theme — read
  • installation — unclassified
  • list_components — read
  • v2_to_v3_code_review — unclassified

handshake and tools listed without a recorded key or OAuth

Score 95/100 · Tools 7 · Token cost approx. 1,561 tokens · Compare · Last tested 2026-11-11 · Version tested 2.1.1 · Package @chakra-ui/react-mcp · Repo chakra-ui/chakra-ui

Summary: Chakra UI MCP (official) completed an MCP handshake without credentials and exposed 7 tools.

Evidence summary

Handshake
pass
Tools listed
7
Context cost
approx. 1561 tokens, cl100k estimate (7 tools, measured 2026-11-11, version 2.1.1; an estimate) ranking · add up your servers' context cost
API key
No key needed for the tools we called
Tested
2026-11-11

Test results

TestResultPointsEvidence
installpass20npm install @chakra-ui/react-mcp (Node 20, Linux) succeeded in 1s.
handshakepass30MCP initialize + tools/list over stdio succeeded with no credentials; 7 tools listed in 2.8s.
maintenancepass25Repo pushed 0 days before test; 40,723 GitHub stars.
docspartial10install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package).
licensepass10MIT (OSI-approved).

Local-model readiness

Token cost (estimate): approx. 1561 tokens, cl100k estimate for 7 tools · about 19% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-11

  • Install from the registry
  • We connected with no credentials and asked for its tool list: it listed 7 tools (Method details: MCP initialize then tools/list)
  • Maintenance signals (last push, archived/deprecated status)
  • Docs (README length, install and config example)
  • License (OSI-approved or not)
  • Token cost (estimate)

Not tested

  • Security: not audited (no code review, no permission or data-flow analysis)
  • Real tasks (no functional task runs yet)
  • Behaviour with real credentials or a real account
  • Performance, rate limits or load
  • Correctness of results beyond the listed tasks

Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.

Known security issues

Checked on 2026-11-11 for version 2.1.1 against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

No published advisories found in OSV and GitHub advisories for @chakra-ui/react-mcp 2.1.1 as of 2026-11-11. This is not a security audit.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Baseline recorded from the 2026-11-11 test run; changes appear after the next test.

Snapshot hash (fingerprint of the tool list)

3f3f3a95f2e3: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "@chakra-ui/react-mcp",
  "version": "2.1.1",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 7,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @chakra-ui/react-mcp` (Node 20, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 7 tools listed in 2.8s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 40,723 GitHub stars."
    ],
    "docs": [
      "partial",
      10,
      "install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
    ],
    "license": [
      "pass",
      10,
      "MIT (OSI-approved)."
    ]
  }
}

Install

npx -y @chakra-ui/react-mcp

Pin the version we tested

npx -y @chakra-ui/react-mcp@2.1.1

tested 2026-11-11. Newer versions may differ and were not tested by us.

{
  "mcpServers": {
    "chakra-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chakra-ui/react-mcp@2.1.1"
      ]
    }
  }
}

Tools listed

customize_theme, get_component_example, get_component_props, get_theme, installation, list_components, v2_to_v3_code_review

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "chakra-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chakra-ui/react-mcp"
      ]
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. Run npm install @chakra-ui/react-mcp (Node 20). This is the exact command we ran on 2026-11-11.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (7 in our test).
{
  "mcpServers": {
    "chakra-ui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chakra-ui/react-mcp"
      ]
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

Related: Best dev MCP servers

FAQ

Is Chakra UI MCP deprecated?

No. @chakra-ui/react-mcp was not deprecated or archived when we last tested it on 2026-11-11.

What replaces Chakra UI MCP?

Nothing; Chakra UI MCP (official) is not deprecated as of 2026-11-11.

Does Chakra UI MCP need an API key?

No. It completed an MCP handshake with no credentials and listed 7 tools.

Embed the badge

TestedMCP: 95/100, tested 2026-11-11

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue