mcpField
P

Packkit

Local
github.com/PackkitJSDeveloper Tools0Updated 4w ago
Repository

About Packkit

Packkit is an MCP server for AI agents that scaffolds and plans upgrades for JavaScript/TypeScript, Python, and Go projects. It provides generator discovery and schema inspection, plus project previews before writing files.

Key features

  1. 01JavaScript/TypeScript, Python, and Go generators
  2. 02List generators and presets
  3. 03Inspect generator options and defaults
  4. 04Preview or scaffold projects
  5. 05Plan upgrades without writing files

Use cases

  1. 01Start a library, CLI, service, SPA, or monorepo
  2. 02Preview a generated project's files and stack
  3. 03Plan template updates against existing edits

MCP support

Exposes Packkit generators to MCP clients through tools for discovery, configuration, project generation, and upgrade planning. It also provides `compose_fullstack` to combine a frontend and backend into one repository.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "packkitjs-packkit": {
      "command": "npx",
      "args": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
Run commandnpx -y packkit-mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmpackkit-mcp1.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

packkit-mcp

npm M8ven Score

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.