# Tools changed: MUI MCP (official)

> Source: <https://testedmcp.com/tools/mui-mcp/#tool-changes>
> Published: 2026-11-13 00:00:00+00:00

# MUI MCP (official)

**100**/100

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. [Methodology](https://testedmcp.com/methodology/)

- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10

Tested npm @mui/mcp 0.1.9 (MIT; repo mui/mui-x packages/mcp, 5,876 GitHub stars when checked). Stdio, 3 tools (useMuiDocs, fetchDocs, generateReactCode), no account. tools/list first showed 2 tools; useMuiDocs registers only after the docs catalog loads (3 tools about 8 s after start), so our first call failed with 'Tool useMuiDocs not found' and was rerun after waiting. Real calls: useMuiDocs for @mui/material returned the Material UI 9.5.0 docs index, and fetchDocs returned the React Button page.

Tool-call test (2026-11-11, direct MCP stdio client, no LLM): **pass**. 2 of 2 read calls passed (after waiting for the late-registered useMuiDocs tool), no key. Evidence: local test run, Nov 11, 2026.

**Transport (tested 2026-11-11):** stdio

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

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

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

- `fetchDocs` — read
- `generateReactCode` — unclassified
- `useMuiDocs` — unclassified

handshake and tools listed without a recorded key or OAuth

Score **100/100** · Tools **3** · Token cost **approx. 2,788 tokens** · [Compare](https://testedmcp.com/compare/?s=mui-mcp) · Last tested **2026-11-11** · Version tested `0.1.9` · Package [@mui/mcp](https://www.npmjs.com/package/@mui/mcp)[mui/mui-x](https://testedmcp.com/go/mui-mcp/)

Summary: MUI MCP (official) completed an MCP handshake without credentials and exposed 3 tools.

## Evidence summary

- Handshake
- pass
- Tools listed
- 3
- Context cost
- approx. 2788 tokens, cl100k estimate (3 tools, measured 2026-11-11, version 0.1.9; an estimate) [ranking](https://testedmcp.com/best/lowest-context-cost-mcp-servers/) ·[add up your servers' context cost](https://testedmcp.com/guides/how-much-context-mcp-servers-cost/)
- API key
- No key needed for the tools we called
- Tested
- 2026-11-11

## Test results

| Test | Result | Points | Evidence | 
|---|---|---|---|
| install | pass | 20 | `npm install @mui/mcp` (Node 20, Linux) succeeded in 1s. | 
| handshake | pass | 30 | MCP `initialize` +`tools/list` over stdio succeeded with no credentials; 3 tools listed in 2.9s. | 
| maintenance | pass | 25 | Repo pushed 0 days before test; 5,876 GitHub stars. | 
| docs | pass | 15 | README over 3,000 chars; 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). | 

## Local-model readiness

Token cost (estimate): **approx. 2788 tokens, cl100k estimate** for 3 tools · about 34% 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 3 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](https://testedmcp.com/methodology/). 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 `0.1.9` against OSV, GitHub advisories, GitHub repository advisories. Scope: the package itself; dependencies not scanned.

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

Monthly roundup: [MCP security issues, October 2026](https://testedmcp.com/security/2026-10/).

## Tool list changes ↻ Tools changed (non-breaking) 2026-11-13

**Tool list changed since last test (2026-11-11 → 2026-11-13): 1 tool description changed: useMuiDocs.** Confirmed by a re-run with the same arguments.

## Show the diff

- Changed description: `useMuiDocs`

## Snapshot hash (fingerprint of the tool list)

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

## Raw test record (JSON)

```
{
  "name": "@mui/mcp",
  "version": "0.1.9",
  "registry": "npm",
  "status": "working",
  "tested": "2026-11-11",
  "tools_count": 3,
  "deprecated": false,
  "archived": false,
  "tests": {
    "install": [
      "pass",
      20,
      "`npm install @mui/mcp` (Node 20, Linux) succeeded in 1s."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 3 tools listed in 2.9s."
    ],
    "maintenance": [
      "pass",
      25,
      "Repo pushed 0 days before test; 5,876 GitHub stars."
    ],
    "docs": [
      "pass",
      15,
      "README over 3,000 chars; 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 @mui/mcp`

## Pin the version we tested

`npx -y @mui/mcp@0.1.9`

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

```
{
  "mcpServers": {
    "mui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mui/mcp@0.1.9"
      ]
    }
  }
}
```

## Tools listed

`fetchDocs`, `generateReactCode`, `useMuiDocs`

Tool history: captured Nov 13, 2026. [All tool history](https://testedmcp.com/changes/).

## Quick config

```
{
  "mcpServers": {
    "mui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mui/mcp"
      ]
    }
  }
}
```

[Add to config](https://testedmcp.com/free-tools/mcp-config-generator/?s=mui-mcp) Opens the config generator with this server selected.

## Setup

1. **Install.** Run`npm install @mui/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 (3 in our test).

```
{
  "mcpServers": {
    "mui-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@mui/mcp"
      ]
    }
  }
}
```

## Test history

- 2026-11-13: Tools changed (non-breaking)
- 2026-11-11: New

Related: [Best dev MCP servers](https://testedmcp.com/best/dev-mcp-servers/) · [Troubleshooting: Tool not found after start](https://testedmcp.com/troubleshooting/mcp-tool-not-found-right-after-start/)

## FAQ

### Is MUI MCP deprecated?

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

### What replaces MUI MCP?

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

### Does MUI MCP need an API key?

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

## Embed the badge

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.