Packkit

io.github.PackkitJSPublished by GitHub account PackkitJSv1.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.PackkitJS/packkit-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account PackkitJS for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.PackkitJS%2Fpackkit-mcp.svg)](https://sourceweft.com/mcp/io.github.PackkitJS%2Fpackkit-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant scaffold and upgrade JavaScript/TypeScript, Python, and Go projects from Packkit generators, including fullstack compositions.

What you can do: Packkit fronts Packkit project generators through a shared protocol, so an assistant can list generators and presets, read a generator's full option schema, and preview or write a new project. Tools include list_generators, list_presets, get_generator_schema, generate_project, and compose_fullstack, which stitches a static frontend and a service backend into one repository. plan_upgrade produces a baseline-aware three-way upgrade plan for an existing project without writing anything.
When to use it: Useful when starting a new library, CLI, service, SPA, monorepo, or fullstack repository and you want the assistant to pick a generator, choose options, and scaffold files. Also useful for planning upgrades to an existing generated project before making changes.
Requirements: Runs locally over stdio as an npm package, launched with npx, so Node.js and network access to fetch the package are needed. No authentication, environment variables, or headers are declared. Desktop MCP clients only; no web executable.

Before you install

generate_project with write: true scaffolds files to disk, so review the previewed file tree before allowing writes. plan_upgrade writes nothing. No credentials, payments, or third-party data sharing are declared.

Installation

In SourceWeft

Open Packkit in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

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):

json

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

{  "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 installnpm run smoke     # boot the server over MCP stdio and exercise all three generatorsnpm run check     # server.json sync check + smoke (what CI runs)

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

Releases are automated with Changesets — see RELEASING.md.

License

MIT © DanMat

Source: README.md at commit 57b5832

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts