Skip to content

Summary

Mantine's official documentation server: gives an agent the component list, per-component docs and the exact props table, so generated React code matches the installed version.

Features

  • Four tools: list_items, get_item_doc, get_item_props and search_docs
  • Real props tables fetched before generation, instead of remembered ones
  • No install and no API key — runs via npx
  • MANTINE_MCP_DATA_URL to point at a pinned or self-hosted docs set
  • Versioned with the Mantine library itself, so docs match the installed release

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Mantine MCP Server" tools will be available.
{
  "mcpServers": {
    "mantine-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@mantine/mcp-server"
      ]
    }
  }
}

Description

Component libraries are where coding agents quietly go wrong — a prop renamed two majors ago, a component that moved packages, a style API that changed shape. The model is confidently describing a version it saw in training rather than the one in your package.json. Mantine's answer is this MCP server, maintained inside the Mantine monorepo and versioned alongside the library itself.

It is small on purpose, with four tools: list_items enumerates what the library offers, get_item_doc returns the documentation for one component or hook, get_item_props returns its props table, and search_docs searches across the documentation. get_item_props is the one that earns its place — props are exactly the detail a model hallucinates, and fetching the real table before writing JSX removes a whole class of "that prop doesn't exist" errors.

It runs with no install (npx @mantine/mcp-server) and no API key. Data is fetched from https://mantine.dev/mcp by default, overridable with MANTINE_MCP_DATA_URL for a pinned or self-hosted documentation set, with MANTINE_MCP_TIMEOUT_MS controlling the HTTP timeout (10000 ms by default).

MIT licensed, published as @mantine/mcp-server from packages/@mantine/mcp-server in the mantinedev/mantine repository. Its version tracks Mantine's own release line, so the documentation an agent reads is the documentation for the release it is generating against.

Related MCP Servers

New

Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.

New

Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.

New

Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.

MCP: Headroom

by Headroom Labs

New

Context-compression MCP server that shrinks tool outputs, logs, files and RAG chunks before they reach the model, cutting 60-95% of tokens on JSON payloads.

Browse all MCP servers →