packkit-mcp

The Packkit Model Context Protocol server — let AI agents (Claude Desktop, Cursor, VS Code, …) scaffold and upgrade modern projects as a native tool. It fronts every Packkit generator through the @packkit/core protocol, so the same tools work across languages:

• JavaScript / TypeScript — create-packkit (libraries, CLIs, services, SPAs, monorepos)
• Python — create-packkit-py (library, CLI, worker, HTTP service)
• Go — create-packkit-go (library, CLI, worker, HTTP service)

It also exposes a compose_fullstack tool that stitches a static frontend + a service backend from any generators into one fullstack repo (e.g. React + FastAPI).

Adding a language later is one registry.register(...) line here — the tools don't change.

Install

Point your MCP client at the published package (no install needed — npx fetches it):

{
  "mcpServers": {
    "packkit": {
      "command": "npx",
      "args": ["-y", "packkit-mcp"]
    }
  }
}

Tools

| Tool | What it does | | --- | --- | | list_generators | List every generator (language target) with maturity + capabilities. Start here. | | list_presets | List a generator's presets (experimental hidden unless asked). | | get_generator_schema | A generator's full option schema (options, choices, defaults). | | generate_project | Preview a project (file tree + stack + deployment contract), or write: true to scaffold to disk. | | plan_upgrade | Baseline-aware three-way upgrade plan for an existing project — template changes vs your edits, writes nothing. |

The typical flow: list_generators → list_presets / get_generator_schema → generate_project. All generation is protocol-driven; the server holds no language-specific logic.

Develop

npm install
npm run smoke     # boot the server over MCP stdio and exercise all three generators
npm run check     # server.json sync check + smoke (what CI runs)

Releases are automated with Changesets — see RELEASING.md.

License

MIT © DanMat