# Packkit (npm · packkit-mcp)

Scaffold, compose, and upgrade modern multi-language projects as a native tool for AI agents.

- Trust score: 93/100 (high trust)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `packkit-mcp`: 93/100 (this document), [markdown](https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp.md), [page](https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp)

## Channel facts

- Registry: `npm`
- Package: `packkit-mcp`
- Version: `1.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 32 of 106 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to PackkitLabs/packkit-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 33 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 821 tokens (~136/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Packkit MCP server?

Packkit runs locally as an npm package, launched with npx -y packkit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add packkitlabs-packkit-mcp -- npx -y packkit-mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "packkitlabs-packkit-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add packkitlabs-packkit-mcp -- npx -y packkit-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "packkitlabs-packkit-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "packkit-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add packkitlabs-packkit-mcp --command npx --arg -y --arg packkit-mcp
```

### Hermes

```yaml
mcp_servers:
  packkitlabs-packkit-mcp:
    command: "npx"
    args: ["-y", "packkit-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "packkitlabs-packkit-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "packkit-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add packkitlabs-packkit-mcp -t stdio -c npx -a -y packkit-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 92, −2)

- [functional] Stability: pass → 0.80

### 2026-09-16 (score 94, 0)

- [security] Stability: 0.97 → pass

### 2026-09-15 (score 94, 0)

- [functional] Stability: pass → 0.97

### 2026-09-14 (score 94, 0)

- [security] Stability: 0.97 → pass

### 2026-09-12 (score 94, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `list_generators` (~63 tokens)

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, then call list_presets and get_generator_schema for it before generating.

### `list_presets` (~108 tokens)

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 includeExperimental is true. Choose a preset that matches the shape the user wants instead of guessing.

Input parameters:

- `generator` (string, required): Generator id from list_generators (e.g. "javascript", "python", "go")
- `includeExperimental` (boolean): Include experimental presets (default false)

### `get_generator_schema` (~63 tokens)

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.

Input parameters:

- `generator` (string, required): Generator id from list_generators

### `generate_project` (~190 tokens)

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 <directory>/<name>. Existing files are never overwritten unless force is set. Call list_presets / get_generator_schema first.

Input parameters:

- `config` (object): Options from get_generator_schema (overrides the preset)
- `directory` (string): Parent directory to create <name>/ in when writing (default: cwd)
- `force` (boolean): Overwrite colliding existing files when writing (default false)
- `generator` (string, required): Generator id from list_generators
- `name` (string, required): Project/package name (also the folder name when writing)
- `preset` (string): A preset (or alias) from list_presets
- `write` (boolean): Write files to disk (default false = preview only)

### `plan_upgrade` (~140 tokens)

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 nothing is clobbered. Reports the plan only — it writes nothing. Requires a generator that supports baseline-upgrade.

Input parameters:

- `config` (object): The options it was generated with
- `directory` (string, required): Path to the existing scaffolded project
- `generator` (string, required): Generator id from list_generators
- `name` (string, required): Project name (as originally generated)
- `preset` (string): The preset it was generated from (if any)

### `compose_fullstack` (~257 tokens)

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. Language-neutral: e.g. a "javascript" react-app frontend + a "python" py-service (or "go" go-service) backend. By default PREVIEWS; pass write: true to scaffold under <directory>/<name>.

Input parameters:

- `backend` (object, required): The service backend to generate: { generator, name, preset?, config? }
- `backendDir` (string): Subdir for the backend (default apps/server)
- `directory` (string): Parent directory to create <name>/ in when writing
- `dockerCompose` (boolean): Emit a root docker-compose.yml (default true)
- `force` (boolean): Overwrite colliding existing files when writing
- `frontend` (object, required): The static frontend to generate: { generator, name, preset?, config? }
- `frontendDir` (string): Subdir for the frontend (default apps/web)
- `name` (string, required): Repo name (folder when writing; README heading)
- `write` (boolean): Write files to disk (default false = preview only)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp#diagnostics

## Score history

- 2026-09-20: 93
- 2026-09-19: 93
- 2026-09-18: 92
- 2026-09-17: 92
- 2026-09-16: 94
- 2026-09-15: 94
- 2026-09-14: 94
- 2026-09-13: 94
- 2026-09-12: 94
- 2026-09-11: 93
- 2026-09-10: 93
- 2026-09-09: 92
- 2026-09-08: 92
- 2026-09-07: 91
- 2026-09-06: 91
- 2026-09-05: 90
- 2026-09-04: 90
- 2026-09-03: 89
- 2026-09-02: 89
- 2026-09-01: 88
- 2026-08-31: 88
- 2026-08-30: 87
- 2026-08-29: 87
- 2026-08-28: 87
- 2026-08-27: 86
- 2026-08-26: 86
- 2026-08-25: 84
- 2026-08-24: 84
- 2026-08-23: 83
- 2026-08-22: 82

## Common questions

### What is the Packkit MCP server?

Packkit is an MCP server listed in the public MCP registry as io.github.PackkitLabs/packkit-mcp. Scaffold, compose, and upgrade modern multi-language projects as a native tool for AI agents. This page covers its npm package (packkit-mcp).

### Is the Packkit MCP server safe to use?

Packkit scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Packkit MCP server expose?

Packkit exposes 6 tools: list_generators, list_presets, get_generator_schema, generate_project, plan_upgrade, compose_fullstack. Their descriptions and schemas cost roughly 821 tokens of context every time the server is loaded.

### Is the Packkit MCP server still maintained?

Packkit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Packkit MCP server under?

Packkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/packkit-mcp
- Socket report: https://socket.dev/npm/package/packkit-mcp
- Repository: https://github.com/PackkitLabs/packkit-mcp
- Changelog RSS feed: https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/packkitlabs-packkit-mcp/packkit-mcp