fumadocs-mcp
Fumadocs MCP Server
An MCP (Model Context Protocol) server that provides AI tools with access to Fumadocs documentation. This makes it easier for AI assistants to help you integrate Fumadocs into your existing projects.
Features
Search documentation - Find relevant docs by keyword
Browse topics - Explore documentation sections
Fetch pages - Get full content of any documentation page
Setup guides - Get framework-specific installation instructions
Component docs - Get UI component documentation with props and examples
Related MCP server: Dedalus MCP Documentation Server
Installation
Using npx (recommended)
npx fumadocs-mcpGlobal installation
npm install -g fumadocs-mcp
fumadocs-mcpFrom source
git clone https://github.com/k4cper-g/fumadocs-mcp
cd fumadocs-mcp
npm install
npm run buildConfiguration
Claude Desktop
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"fumadocs": {
"command": "npx",
"args": ["fumadocs-mcp"]
}
}
}Or if installed from source:
{
"mcpServers": {
"fumadocs": {
"command": "node",
"args": ["/path/to/fumadocs-mcp/build/index.js"]
}
}
}Claude Code
The MCP will be automatically available when configured in Claude Desktop.
Available Tools
list_topics
Browse available documentation sections and topics.
Parameters:
- section (optional): "all" | "cli" | "headless" | "framework" | "mdx" | "ui"search_docs
Search documentation by keyword.
Parameters:
- query (required): Search query string
- section (optional): Filter to a specific sectionget_page
Fetch the full content of a documentation page.
Parameters:
- path (required): Documentation path (e.g., "/docs/manual-installation/next")get_setup_guide
Get a complete setup guide for adding Fumadocs to an existing project.
Parameters:
- framework (required): "next" | "react-router" | "tanstack-start" | "waku"
- includeUI (optional): Whether to include UI setup instructions (default: true)get_component
Get documentation for a specific UI component.
Parameters:
- component (required): Component name (e.g., "accordion", "tabs", "codeblock")Example Usage
Once configured, you can ask Claude things like:
"How do I add Fumadocs to my existing Next.js project?"
"Show me how to use the Tabs component in Fumadocs"
"Search for documentation about internationalization"
"What components are available in Fumadocs UI?"
Development
# Install dependencies
npm install
# Build
npm run build
# Run in development mode
npm run dev
# Test with MCP Inspector
npm run inspectorLicense
MIT
Available Tools
5 toolsget_componentC
Get documentation for a specific Fumadocs UI component. Includes props, usage examples, and configuration options. Available components: accordion, tabs, codeblock, steps, files, banner, and more.
Inputs: component (required).
get_pageA
Fetch the full content of a specific Fumadocs documentation page. Provide the path (e.g., '/docs/manual-installation/next') to get detailed documentation.
Inputs: path (required).
get_setup_guideA
Get a complete setup guide for adding Fumadocs to an existing project. Specify the framework (next, react-router, tanstack-start, or waku) to get framework-specific instructions.
Inputs: framework (required), includeUI.
list_topicsA
Browse available Fumadocs documentation sections and topics. Use without parameters to see all sections, or specify a section to see all topics in that section.
Inputs: section.
search_docsB
Search Fumadocs documentation by keyword. Returns matching documentation pages with titles, descriptions, and paths. Use this to find specific topics or features.
Inputs: query (required), section.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_component retrieves UI component details, get_page fetches full page content, get_setup_guide provides framework-specific setup instructions, list_topics browses documentation sections, and search_docs performs keyword searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_component, get_page, get_setup_guide, list_topics, and search_docs. The verbs (get, list, search) are appropriately descriptive and uniform, creating a predictable and readable naming convention throughout the set.
With 5 tools, the server is well-scoped for its purpose of accessing Fumadocs documentation. Each tool serves a specific and necessary function (e.g., retrieving components, pages, setup guides, browsing topics, and searching), with no redundancy or missing core operations, making the count ideal for the domain.
The tool set provides complete coverage for documentation access: it supports retrieving specific components and pages, getting setup instructions, browsing topics, and searching. This covers all typical user workflows (lookup, navigation, and discovery) without obvious gaps, ensuring agents can handle common documentation tasks effectively.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for agentverse documentation, generated by doc2mcp.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
An MCP server that gives your AI access to the source code and docs of all public github repos
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI assistants to access up-to-date documentation for Python libraries like LangChain, LlamaIndex, and OpenAI through dynamic fetching from official sources.1MIT
- AlicenseAqualityDmaintenanceAn MCP server that serves documentation and enables AI-powered search, Q\&A, and document analysis for developer tools and guides.54MIT
- AlicenseNot gradedqualityAmaintenanceSelf-hosted MCP server that indexes documentation from various sources and makes it searchable by AI assistants via the Model Context Protocol and REST API.27 npm89Apache 2.0
- AlicenseNot gradedqualityBmaintenanceAn MCP server that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.18 npmMIT