πΌ A token-friendly local MCP server for DaisyUI component documentation using their public llms.txt.
Config is the same across clients β only the file and path differ.
{
"mcpServers": {
"daisyui-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A token-friendly local MCP server for DaisyUI component documentation
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories β click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience β it helps other developers decide.
Sign in to write a review.
Others in design / developer-tools
A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects β databases, auth, storage, and edge functions
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for Daisyui Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A token-friendly local MCP server for DaisyUI component documentation
Give your AI assistant the power to build beautiful UIs with DaisyUI π
Features β’ Installation β’ Docker β’ Usage β’ Configuration
This server exposes two tools that AI assistants can use:
| Tool | Description |
|---|---|
list_components | π Lists all available DaisyUI components with short descriptions |
get_component | π Gets the full documentation for a specific component (classes, syntax, examples) |
π‘ The component docs are pulled from daisyui.com/llms.txt and stored locally as markdown files. This way you can also add your own custom components or edit existing ones to your liking or project needs.
Try asking your AI assistant:
"What DaisyUI components are available?"
"Implement a responsive card grid using DaisyUI"
"How does the modal component work? Show me an example"
git clone https://github.com/birdseyevue/fastmcp.git
cd fastmcp
python -m venv venv
# Windows
venv\Scripts\activate
# macOS/Linux
source venv/bin/activate
pip install -r requirements.txt
You can also run the MCP server using Docker.
docker build -t daisyui-mcp .
docker run -i --rm daisyui-mcp
docker compose up --build
The docker-compose.yml mounts the local components/ directory as a volume, so any changes you make to component docs on the host are reflected inside the container.
{
"servers": {
"daisyui": {
"command": "docker",
"args": ["run", "-i", "--rm", "daisyui-mcp"]
}
}
}
Upon first run, the MCP server will not have any component docs. Fetch them by running:
python update_components.py
This fetches the latest llms.txt from DaisyUI and generates all the markdown files in /components.
python mcp_server.py
If DaisyUI releases new components or updates their docs, simply run:
python update_components.py
Add the MCP server to your AI assistant's configuration: