daisyui-mcp 0.1.0__tar.gz

daisyui_mcp-0.1.0/.github/workflow.yml

@@ -0,0 +1,4 @@
+# GitHub discovers workflow files under .github/workflows/.
+# The canonical tagged PyPI publisher is .github/workflows/publish.yml.
+# This compatibility note preserves the requested singular path without
+# creating a second, undiscoverable publishing workflow.

daisyui_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  checks:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - name: Check out source
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: latest
+      - name: Set up Python
+        run: uv python install ${{ matrix.python-version }}
+      - name: Install dependencies
+        run: uv sync --locked --extra dev --extra skills
+      - name: Check formatting
+        run: uv run --extra dev ruff format --check .
+      - name: Lint
+        run: uv run --extra dev ruff check .
+      - name: Type-check
+        run: uv run --extra dev mypy src tests
+      - name: Test
+        run: uv run --extra dev pytest
+      - name: Build distributions
+        run: uv run --extra dev python -m build
+      - name: Check distributions
+        run: uv run --extra dev twine check dist/*

daisyui_mcp-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,39 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "v*.*.*"
+
+permissions:
+  contents: read
+
+jobs:
+  publish:
+    name: Build and publish the tagged release
+    runs-on: ubuntu-latest
+    environment:
+      name: release
+      url: https://pypi.org/p/daisyui-mcp
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Check out the tagged source
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: latest
+      - name: Set up Python
+        run: uv python install 3.12
+      - name: Install release tooling
+        run: uv sync --locked --extra dev
+      - name: Build the tagged distributions
+        run: uv run --extra dev python -m build
+      - name: Validate metadata
+        run: uv run --extra dev twine check dist/*
+      - name: Publish with Trusted Publishing
+        uses: pypa/gh-action-pypi-publish@release/v1

daisyui_mcp-0.1.0/.gitignore

@@ -0,0 +1,207 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

daisyui_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,11 @@
+# Changelog
+
+## 0.1.0
+
+- Renewed the fork as a typed Python 3.10+ package with a src layout.
+- Preserved list_components and get_component compatibility tools.
+- Added search, status, refresh, skill, and resource capabilities.
+- Added current DaisyUI component/installation guidance and offline fallback data.
+- Added safe installation of the official DaisyUI agent skill tree.
+- Added strict MyPy, Ruff, pytest, wheel, and Twine validation.
+- Added GitHub Actions CI and Trusted Publishing workflow configuration.

daisyui_mcp-0.1.0/CONTEXT.md

@@ -0,0 +1,25 @@
+# DaisyUI MCP
+
+This context defines the language used by the local server that makes official DaisyUI documentation useful to MCP clients.
+
+## Language
+
+**Component**:
+A DaisyUI UI primitive with a canonical name and official documentation.
+_Avoid_: Widget, control
+
+**Documentation**:
+The Markdown reference material published for DaisyUI components and their usage.
+_Avoid_: Scrape, page dump
+
+**Skill**:
+An official, reusable set of DaisyUI guidance intended to teach an AI tool how to work with the library.
+_Avoid_: Prompt, recipe
+
+**Content source**:
+The official DaisyUI material from which a served component or skill document originates.
+_Avoid_: Feed, endpoint
+
+**Project-local installation**:
+An installation of an official skill into the current project’s designated skills directory.
+_Avoid_: Global installation, user installation

daisyui_mcp-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,31 @@
+# Contributing
+
+## Setup
+
+Use uv and the committed lockfile:
+
+~~~bash
+uv sync --locked --extra dev --extra skills
+~~~
+
+Run the complete local checks before opening a pull request:
+
+~~~bash
+uv run --extra dev ruff check .
+uv run --extra dev ruff format --check .
+uv run --extra dev mypy src tests
+uv run --extra dev pytest
+~~~
+
+## Content changes
+
+Prefer the official DaisyUI sources. Component content belongs under the
+package data directory so wheel installations remain self-contained. Use
+daisyui-mcp refresh or update_components.py when updating the snapshot, and
+review the resulting component changes rather than committing unrelated cache
+files.
+
+## Pull requests
+
+Keep changes focused, add tests for behavior changes, and update the changelog
+when the public MCP surface changes.

daisyui_mcp-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 birdseyevue
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

daisyui_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,131 @@
+Metadata-Version: 2.4
+Name: daisyui-mcp
+Version: 0.1.0
+Summary: A local MCP server for DaisyUI component documentation.
+Requires-Python: <4,>=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: fastmcp<5.0,>=4.0
+Requires-Dist: platformdirs<5.0,>=4.0
+Provides-Extra: skills
+Requires-Dist: httpx<1,>=0.27; extra == "skills"
+Provides-Extra: dev
+Requires-Dist: build<2,>=1.2; extra == "dev"
+Requires-Dist: mypy<3,>=1.15; extra == "dev"
+Requires-Dist: pytest<10,>=8.3; extra == "dev"
+Requires-Dist: ruff<1,>=0.9; extra == "dev"
+Requires-Dist: twine<8,>=6; extra == "dev"
+Dynamic: license-file
+
+# daisyui-mcp
+
+A typed, local Model Context Protocol server for official DaisyUI 5
+documentation and agent skills. It is distributed as a normal Python wheel,
+works with Python 3.10+, and keeps a bundled offline snapshot for predictable
+development.
+
+## Install
+
+Install the MCP server with pip:
+
+~~~bash
+python -m pip install daisyui-mcp
+~~~
+
+Install the server and its optional skill-management dependency:
+
+~~~bash
+python -m pip install "daisyui-mcp[skills]"
+uv tool install "daisyui-mcp[skills]"
+~~~
+
+For local development, sync the committed lockfile:
+
+~~~bash
+uv sync --locked --extra dev --extra skills
+~~~
+
+## Run
+
+The default command serves MCP over stdio:
+
+~~~bash
+daisyui-mcp
+~~~
+
+To configure an MCP client, use the installed executable as its command:
+
+~~~text
+/absolute/path/to/daisyui-mcp/.venv/bin/daisyui-mcp
+~~~
+
+The compatibility module mcp_server.py remains available for older
+checkout-based configurations.
+
+## MCP surface
+
+Tools:
+
+- list_components and get_component(name) preserve the original API.
+- search_daisyui(query) searches component and skill metadata.
+- list_skills() and get_skill(name) expose the bundled official skill.
+- refresh_daisyui() refreshes current component docs with cached fallback.
+- install_daisyui_skills(target) installs the official skill tree.
+- daisyui_status() reports content origin, counts, and refresh time.
+
+Resources:
+
+- daisyui://components
+- daisyui://skills
+- daisyui://install
+- daisyui://status
+- daisyui://component/{name}
+- daisyui://skill/{name}
+
+The MCP server can install skills into the current project with an explicit
+tool call. The CLI equivalent is:
+
+~~~bash
+daisyui-mcp skills install
+daisyui-mcp skills install --target ./custom/skills/daisyui
+~~~
+
+The default target is ./.agents/skills/daisyui. The installer fetches the
+official DaisyUI skill tree, validates archive paths, and falls back to the
+packaged SKILL.md if the network is unavailable.
+
+## DaisyUI source and refresh behavior
+
+The runtime specification follows the official DaisyUI installation guide:
+
+https://daisyui.com/docs/install/
+
+Current component content is fetched from:
+
+https://daisyui.com/llms.txt
+
+daisyui-mcp refresh stores a JSON snapshot in the platform user cache. The
+server serves cached content after a successful prior refresh and bundled
+content when no cache exists or the network is unavailable. The package also
+bundles current component docs, including aura, megamenu, otp, and tooltip,
+plus the official skill entrypoint.
+
+## Development
+
+~~~bash
+uv sync --locked --extra dev --extra skills
+uv run --extra dev ruff check .
+uv run --extra dev ruff format --check .
+uv run --extra dev mypy src tests
+uv run --extra dev pytest
+uv run --extra dev python -m build
+uv run --extra dev twine check dist/*
+~~~
+
+The project uses a src layout, setuptools with setuptools-scm, strict MyPy,
+Ruff, pytest, and a committed uv.lock. Git tags such as v0.1.0 determine
+the package version used by the release workflow.
+
+## License
+
+MIT. See LICENSE.

daisyui_mcp-0.1.0/PLAN.md

@@ -0,0 +1,9 @@
+# Implementation slices
+
+- [x] T001: Establish the src-layout package, typed public API skeleton, Git-BBQ context, initial ADR, and development tooling configuration.
+- [x] T002: Import current DaisyUI component documentation and official skill resources with attribution and package-data configuration.
+- [x] T003: Implement the typed content store, runtime source synchronization, persistent cache fallback, validation, and maintainer CLI commands.
+- [x] T004: Implement backward-compatible MCP tools plus typed component, installation, skill, and status resources using FastMCP.
+- [x] T005: Add strict mypy coverage and pytest unit/integration tests for content, synchronization, cache, path safety, MCP behavior, and CLI installation.
+- [x] T006: Complete README, CHANGELOG, contributor/security guidance, CI checks, wheel metadata, and tag-triggered OIDC PyPI publishing workflow.
+- [x] T007: Verify pip and uv-tool installation from the built wheel, repair all failed checks, and leave a release-ready local tree.

daisyui_mcp-0.1.0/README.md

@@ -0,0 +1,112 @@
+# daisyui-mcp
+
+A typed, local Model Context Protocol server for official DaisyUI 5
+documentation and agent skills. It is distributed as a normal Python wheel,
+works with Python 3.10+, and keeps a bundled offline snapshot for predictable
+development.
+
+## Install
+
+Install the MCP server with pip:
+
+~~~bash
+python -m pip install daisyui-mcp
+~~~
+
+Install the server and its optional skill-management dependency:
+
+~~~bash
+python -m pip install "daisyui-mcp[skills]"
+uv tool install "daisyui-mcp[skills]"
+~~~
+
+For local development, sync the committed lockfile:
+
+~~~bash
+uv sync --locked --extra dev --extra skills
+~~~
+
+## Run
+
+The default command serves MCP over stdio:
+
+~~~bash
+daisyui-mcp
+~~~
+
+To configure an MCP client, use the installed executable as its command:
+
+~~~text
+/absolute/path/to/daisyui-mcp/.venv/bin/daisyui-mcp
+~~~
+
+The compatibility module mcp_server.py remains available for older
+checkout-based configurations.
+
+## MCP surface
+
+Tools:
+
+- list_components and get_component(name) preserve the original API.
+- search_daisyui(query) searches component and skill metadata.
+- list_skills() and get_skill(name) expose the bundled official skill.
+- refresh_daisyui() refreshes current component docs with cached fallback.
+- install_daisyui_skills(target) installs the official skill tree.
+- daisyui_status() reports content origin, counts, and refresh time.
+
+Resources:
+
+- daisyui://components
+- daisyui://skills
+- daisyui://install
+- daisyui://status
+- daisyui://component/{name}
+- daisyui://skill/{name}
+
+The MCP server can install skills into the current project with an explicit
+tool call. The CLI equivalent is:
+
+~~~bash
+daisyui-mcp skills install
+daisyui-mcp skills install --target ./custom/skills/daisyui
+~~~
+
+The default target is ./.agents/skills/daisyui. The installer fetches the
+official DaisyUI skill tree, validates archive paths, and falls back to the
+packaged SKILL.md if the network is unavailable.
+
+## DaisyUI source and refresh behavior
+
+The runtime specification follows the official DaisyUI installation guide:
+
+https://daisyui.com/docs/install/
+
+Current component content is fetched from:
+
+https://daisyui.com/llms.txt
+
+daisyui-mcp refresh stores a JSON snapshot in the platform user cache. The
+server serves cached content after a successful prior refresh and bundled
+content when no cache exists or the network is unavailable. The package also
+bundles current component docs, including aura, megamenu, otp, and tooltip,
+plus the official skill entrypoint.
+
+## Development
+
+~~~bash
+uv sync --locked --extra dev --extra skills
+uv run --extra dev ruff check .
+uv run --extra dev ruff format --check .
+uv run --extra dev mypy src tests
+uv run --extra dev pytest
+uv run --extra dev python -m build
+uv run --extra dev twine check dist/*
+~~~
+
+The project uses a src layout, setuptools with setuptools-scm, strict MyPy,
+Ruff, pytest, and a committed uv.lock. Git tags such as v0.1.0 determine
+the package version used by the release workflow.
+
+## License
+
+MIT. See LICENSE.

daisyui_mcp-0.1.0/SECURITY.md

@@ -0,0 +1,14 @@
+# Security policy
+
+## Reporting a vulnerability
+
+Please do not open a public issue for a suspected vulnerability. Contact the
+maintainer at averyfreeman@gmail.com with a description, reproduction steps,
+and the affected version.
+
+## Runtime safety
+
+The refresh operation has bounded response sizes and timeout-controlled network
+requests. Skill installation extracts only files below the official
+skills/daisyui archive subtree and rejects traversal paths. Installation is
+explicit; the package does not write project files during import.

daisyui_mcp-0.1.0/TASK.md

@@ -0,0 +1,20 @@
+## Goal
+
+Renew the DaisyUI MCP server from the edited source snapshot, align it with the current DaisyUI 5 documentation and official skills, make the Python package fully typed and pip/uv-installable, and prepare a verified PyPI release for `daisyui-mcp`.
+
+## Acceptance criteria
+
+- The project uses a typed `src/daisyui_mcp` package with setuptools-scm versioning, `py.typed`, compatible runtime dependency ranges, and a committed `uv.lock`.
+- The MCP server preserves `list_components` and `get_component`, and adds typed discovery, search, skill, refresh, status, and resource capabilities aligned with the current DaisyUI documentation model.
+- Current official DaisyUI component documentation and skill resources are bundled with attribution, refreshed at runtime with bounded network access, and served through validated persistent-cache fallback behavior.
+- `daisyui-mcp skills install` supports project-local installation by default and an explicitly supplied CLI target; MCP installation is restricted to the project-local skills directory.
+- Production code, CLI code, synchronization code, and tests have complete type annotations and pass strict mypy checks.
+- Unit and integration tests cover parsing, lookup, refresh failures, cache fallback, path safety, MCP calls/resources, CLI installation, and package contents.
+- Ruff, pytest, mypy, wheel/sdist build, and twine metadata validation pass through the verification command below.
+- README, CONTEXT.md, native ADR records, CHANGELOG.md, CI workflow, and OIDC PyPI publish workflow document the supported installation and release process.
+
+## Verification
+
+```sh
+uv run --extra dev ruff check . && uv run --extra dev ruff format --check . && uv run --extra dev mypy src tests && uv run --extra dev pytest && temp_dist="$(mktemp -d)" && uv run --extra dev python -m build --outdir "$temp_dist" && uv run --extra dev twine check "$temp_dist"/*
+```