Packkit
Scaffold, compose, and upgrade modern multi-language projects as a native tool for AI agents.
Open source Open in the app JSON README (API)
About
Scaffold, compose, and upgrade modern multi-language projects as a native tool for AI agents.
Details
- Kind
- MCP servers
- Topic
- Developer tools
- Publisher
- packkitlabs
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 1.2.1
- Last push
- 2026-08-17T09:46:22Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT
- Added
- 2026-08-29 03:02:09
- Updated
- 2026-08-29 03:02:09
- Origin id
io.github.PackkitLabs/packkit-mcp
README
# packkit-mcp
[](https://www.npmjs.com/package/packkit-mcp)
The **Packkit** [Model Context Protocol](https://modelcontextprotocol.io) 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`](https://github.com/PackkitLabs/packkit-core) protocol, so the same
tools work across languages:
- **JavaScript / TypeScript** — [`create-packkit`](https://github.com/PackkitLabs/create-packkit-js) (libraries, CLIs, services, SPAs, monorepos)
- **Python** — [`create-packkit-py`](https://github.com/PackkitLabs/create-packkit-py) (library, CLI, worker, HTTP service)
- **Go** — [`create-packkit-go`](https://github.com/PackkitLabs/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):
```json
{
"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
```sh
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](https://github.com/changesets/changesets) —
see [RELEASING.md](./RELEASING.md).
## License
MIT © DanMat