fumadocs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| search_docsB | Search Fumadocs documentation by keyword. Returns matching documentation pages with titles, descriptions, and paths. Use this to find specific topics or features. |
| 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. |
| 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. |
| get_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.