Official Duck Framework MCP server for AI-assisted development and project scaffolding.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 13 tools
Most tools have distinct purposes: docs discovery (list_doc_categories, search_docs), guide retrieval (get_ai_guides, fetch_ai_guide), structure lookups, and scaffolding are clearly separated. The three structural tools (get_blueprint_locations, get_blueprint_structure, get_project_structure) and the get_ai_guides/fetch_ai_guide pair could momentarily be confused, but descriptions clarify the boundaries.
All names are snake_case verb_noun (get_*, list_*, scaffold_*, lint_*, plan_*, search_*, reindex_*), which is highly readable and predictable. The minor inconsistency is the get_ai_guides/fetch_ai_guide pair mixing the verbs get and fetch for a complementary list/retrieve flow.
13 tools is well within the appropriate range and each earns its place across the documentation, structure, scaffolding, and validation lifecycle. No obvious redundant or filler tools.
The surface covers discovery, search, guide fetching, structural reference, scaffolding, linting, and feature planning—a strong end-to-end flow for a framework coding assistant. Minor gap: there is no explicit tool to fetch the full content of a specific documentation page surfaced by search_docs or list_doc_categories, which could be a dead end when guides don't cover a topic.
Fetch an official Duck Framework AI guide. Use this after get_ai_guides() to retrieve the full guide content for AI-assisted Duck Framework development. Always read the relevant guide before generating code instead of relying on memory.
Inputs: guide (required).
List available Duck Framework AI guides. Use this to discover available guides before fetching one with fetch_ai_guide(). Returns guide identifiers and their descriptions.
Inputs: no named parameters.
Explain where Duck Framework blueprints can be located. Describes the supported blueprint layouts and when each organization approach is appropriate.
Inputs: no named parameters.
Return the standard internal structure of a Duck Framework blueprint. Use this before generating a new blueprint or adding files to an existing one to understand where components, pages, templates, automations, and views belong.
Inputs: no named parameters.
Look up a built-in Duck Framework component API. Returns the confirmed import path, container type, and supported keyword arguments for a component without requiring the full HTML components guide to be loaded. Use this before using any component that has not already been confirmed. Returns close-name suggestions when the component does not exist.
Inputs: component_name (required).
Return the standard Duck Framework project directory structure. Use this before creating or modifying projects to understand where files and directories belong.
Inputs: no named parameters.
Check Duck Framework component or page code for common mistakes. Detects known patterns such as incorrect component imports, invalid page imports, incorrect Heading usage, leading-underscore method names, and separator comments. This is a pattern check for known issues, not a complete correctness validator. An empty result only means no known issues were detected. Run this on generated component code before presenting it as final.
Inputs: code (required).
List all Duck Framework documentation categories and their pages. Use this when browsing available documentation without a specific search query.
Inputs: version.
Analyze a Duck Framework feature request and create an implementation plan. Returns relevant documentation to read and a suggested order of operations before writing code. Use this before implementing non-trivial Duck Framework features.
Inputs: request (required), version.
Rebuild the Duck Framework documentation index. Crawls the live documentation sitemap for a given version and merges the result in: curated tags/summary/category are preserved, new pages are added, and pages no longer in the sitemap are removed. Requires the admin scope.
Inputs: version.
Scaffold a new Duck Framework blueprint. Generates a blueprint structure containing blueprint.py, views.py, and optional UI, template, and static directories following the documented Duck blueprint conventions. Returns generated file contents and the settings configuration needed to register the blueprint. This tool does not write files.
Inputs: blueprint_name (required), urlpatterns, enable_static_dir, enable_template_dir, +1 more.
Scaffold a new Duck Framework project. Returns the required CLI commands and generated file contents for supported features with confirmed APIs. Unsupported features return documentation guidance instead of generated code to avoid guessing framework APIs. This tool does not write files. It only returns generated content for the calling client to add to the user's project directory.
Inputs: project_name (required), features.
Fuzzy-search the Duck Framework documentation. Use this whenever the correct documentation page for a feature is unknown. Returns ranked matches containing title, URL, category, summary, and relevance score.
Inputs: query (required), top_k, version, category.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Official MCP server for Lovable, the AI-powered full-stack app builder.
Official MCP server for Agentwork — delegate tasks to AI agents with human-in-the-loop
An MCP server that gives your AI access to the source code and docs of all public github repos
Add one secure layer between your agents and this server.
