unifi-mcp-tool-builder

You add a new MCP tool by following a phase-driven workflow of research, design, implementation, testing, and documentation that enforces TDD, Pydantic v2 models, and FastMCP tooling conventions. This ensures new UniFi Controller features match existing patterns and pass quality gates.

The best way to scaffold Python MCP tools with TDD is to use ready-made templates for tests, Pydantic v2 models, and API documentation. This generates code skeletons with validation and quality gates already configured for consistent development.

Yes, UniFi MCP tool scaffolding requires FastMCP and Pydantic v2 to maintain consistency with existing patterns. The builder enforces these specific frameworks alongside TDD to generate high-quality artifacts for the MCP Server.

You generate API documentation and changelog updates using best-practice templates provided during the scaffolding phases. This ensures every new UniFi MCP tool includes ready-to-use docs and changelog entries with minimal manual setup.

Yes, you can use this scaffolding workflow for all UniFi MCP tool categories. It applies to any project adding new UniFi Network Controller features as MCP tools, ensuring consistent structure and validation across the entire 74-tool toolset.

Scaffolding MCP tools with a blueprint improves software engineering by enforcing TDD, Pydantic v2 validation, and FastMCP conventions across research, design, and implementation phases. This maintains consistency with existing tools and eliminates structural drift.