
MCP server for Packkit — scaffold, upgrade & compose fullstack projects in any supported language
MCP server for Packkit — scaffold, upgrade & compose fullstack projects in any supported language (JS/TS, Python, Go) as a native AI-agent tool
·
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:
create-packkit (libraries, CLIs, services, SPAs, monorepos)create-packkit-py (library, CLI, worker, HTTP service)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.
Point your MCP client at the published package (no install needed — npx fetches it):
{
"mcpServers": {
"packkit": {
"command": "npx",
"args": ["-y", "packkit-mcp"]
}
}
}| 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.
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.
MIT © DanMat
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add packkit -- npx -y packkit-mcp{
"mcpServers": {
"packkit": {
"args": [
"-y",
"packkit-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"packkit","args":["-y","packkit-mcp"],"command":"npx"}'[mcp_servers.packkit]
command = "npx"
args = ["-y", "packkit-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/packkit-mcp to learn what the "Packkit Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
| Name | What it does |
|---|---|
list_generators | START HERE. Lists every Packkit generator (a language target — e.g. javascript, python, go) with its maturity and protocol capabilities. Pick the generator whose language matches what the user wants, |
list_presets | List the presets a generator offers (e.g. ts-lib, react-lib, node-service for javascript; py-lib, py-cli for python), each with a description and maturity. Experimental presets are hidden unless inclu |
get_generator_schema | Return a generator's full option schema — every option, its choices and defaults — as JSON. Read this before passing a `config` to generate_project so the options you set are valid for that generator. |
generate_project | Generate a project with a generator. By default it PREVIEWS (returns the file tree, stack summary and deployment contract without touching disk); pass write: true to scaffold the files under <director |
plan_upgrade | Plan a re-scaffold of an existing project against the current templates: a three-way diff (baseline vs on-disk vs freshly generated) that separates template changes from the user's own edits, so nothi |
compose_fullstack | Compose two projects — a static frontend and an HTTP service backend, from ANY generators — into one fullstack repo (apps/web + apps/server) with a fullstack deployment contract and a docker-compose. |
Read live from the server on October 2, 2026.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/packkit-mcp)Nothing comparable is listed yet.
v1.2.1Release notesv1.2.0Release notesv1.1.1Release notesv1.1.0Release notesv1.0.2Release notesv1.0.1Release notesv1.0.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "packkit-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.