Packkit

Official registry AI and agents

Scaffold and upgrade modern projects (JS/TS, Python) as a native tool for AI agents.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package packkit-mcp
Claude Code
claude mcp add packkit -- npx -y packkit-mcp@1.1.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "packkit": {
            "command": "npx",
            "args": [
                "-y",
                "packkit-mcp@1.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. packkit-mcp
  2. Install
  3. Tools
  4. Develop
  5. License

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:

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

ToolWhat it does
list_generatorsList every generator (language target) with maturity + capabilities. Start here.
list_presetsList a generator's presets (experimental hidden unless asked).
get_generator_schemaA generator's full option schema (options, choices, defaults).
generate_projectPreview a project (file tree + stack + deployment contract), or write: true to scaffold to disk.
plan_upgradeBaseline-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

Frequently asked questions

What is Packkit?

Scaffold and upgrade modern projects (JS/TS, Python) as a native tool for AI agents.

How do I install Packkit?

It runs on your machine. In Claude Code: claude mcp add packkit -- npx -y packkit-mcp@1.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Packkit need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Packkit open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Packkit?

It is published by PackkitJS. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.