Power your agent
पब्लिशर की अपनी कमांड। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
npx -y @produtype/[email protected]Claude Code में लोकल कमांड के लिए इंस्टॉल लिंक नहीं है। नीचे दी गई कमांड कॉपी करें और टर्मिनल में चलाएँ।
claude mcp add produtype-core -- npx -y @produtype/core@1.36.0टर्मिनल में चलाएँ।
{ "mcpServers": { "produtype-core": { "command": "npx", "args": [ "-y", "@produtype/[email protected]" ] } }}claude_desktop_config.json
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
ProdKit is a deterministic local CLI that analyzes an existing web application repository and generates a production-readiness report or a remediation plan.
It is designed for early-stage and AI-generated apps where architecture and security quality can vary significantly.
ProdKit is read-only: it never modifies the target repository.
Deterministic CLI and library that analyzes a web application repository and reports how far it is from production-ready for the kind of product it is meant to be.
ProdKit inspects a target project and detects:
Then it builds a structured production-readiness report with:
null where too little of the repository could be read
to characterise itinconclusive, prototype, early, partial, production_ready)Two things the report says about its own reading, because a finding is only worth what the reading behind it is:
typescript peer dependency decides whether JavaScript and
TypeScript are parsed; without it they are searched as text, and the report says so
rather than claiming otherwise.unknown, never passed and never missing. Blindness can
turn a verdict into no verdict; it is not allowed to turn one into its opposite.From the report, ProdKit can also build a deterministic remediation plan with phases, task priorities, effort estimates, and test suggestions.
npm install -g @produtype/core
prodkit analyze .
The MCP server needs one extra package, and only if you use it:
npm install @modelcontextprotocol/sdk # for prodkit-mcp
It is an optional peer dependency rather than a dependency because it brings 164 packages with it — nine tenths of what this package used to install — for a server most people never run, along with network, shell and eval access that the analyzer itself does not use. Installing this package alone brings 19.
The command is prodkit; the package is @produtype/core. They differ on purpose:
prodkit on npm is an unrelated and actively maintained package, so this one is
published under the @produtype scope. npm i prodkit installs somebody else's
project.
npm install
npm run build
npm link
After linking, use:
prodkit --help
npm install
npm run build
npm test
Optional lint:
npm run lint
The fixture corpus only contains what somebody wrote into it, so a pattern broad enough to match ordinary code passes it untouched. One did: it changed nothing across 234 fixtures and inferred three real B2B products as marketplaces, because no fixture happens to write a Next.js redirect.
npm run wild clones the repositories listed in scripts/wild-repos.json, records
the profile it infers and the status of every capability, compares that against
scripts/wild-baseline.json, and deletes the sources again. It needs the network, so
it is not part of CI — run it before releasing a change to a detector.
npm run wild # compare against the baseline
npm run wild -- --write # record current behaviour as the baseline
A change it reports is not automatically a regression; it is a change that has to be explained before it ships. Only the verdicts are kept in the repository — no cloned source is retained.
Diagnostic command:
prodkit analyze <path-to-project>
Remediation planning command:
prodkit plan <path-to-project>
Options:
--format markdown|json output format for the report or plan payload--summary print summary only--output <path> write output to file--profile <name> evaluate expected product capabilities (static-site, internal-tool, b2c-app, b2b-saas, ai-saas, marketplace, game, client-app, mobile-app, auto, observed-only)--fail-under <score> (analyze only) exit with code 1 if the overall score is below the threshold — useful as a CI quality gate--min-maturity <level> (analyze only) exit with code 1 if maturity is below prototype|early|partial|production_ready--ai (analyze only) add an AI stack/architecture insight — opt-in, advisory only, does not affect the score--ai-review (analyze only) add an AI semantic review of fine-grained code issues — opt-in, advisory only, does not affect the scoreOptional AI layer:
@produtype/ai, which is commercial
and is not a dependency of this package. An open source install runs the
deterministic analysis only, and --ai reports that the package is not installed
rather than failing. That package brings its own model access; nothing needs to be
configured here to run the analysis.@produtype/ai is installed, it redacts secrets from repository content before
sending anything, and its output stays advisory — it never changes the deterministic
score.Profile warning:
--profile to evaluate expected product capabilities.Inconclusive assessments:
overallScore is null and the
maturity level is inconclusive. It used to cap the score at 39 instead, which was
a number standing where an answer was missing.prodkit analyze ../my-app
prodkit analyze ../my-app --profile b2b-saas
prodkit analyze ../my-app --profile auto
prodkit analyze ../my-app --summary
prodkit analyze ../my-app --format markdown
prodkit analyze ../my-app --format json
prodkit analyze ../my-app --output prodkit-report.md
prodkit analyze tests/fixtures/express-basic --format json --output report.json
prodkit analyze ../my-app --fail-under 65
prodkit analyze ../my-app --min-maturity partial
prodkit plan ../my-app
prodkit plan ../my-app --profile b2b-saas
prodkit plan ../my-app --profile observed-only
prodkit plan ../my-app --format markdown
prodkit plan ../my-app --format json
prodkit plan ../my-app --output prodkit-plan.md
Generated from the analyzer itself — run npm run docs:stacks after changing a detector.
How some of these are decided:
A hosted platform is recorded separately from the engine underneath it, so rules written about an engine keep working without knowing about the host, while "this data lives on infrastructure someone else operates" stays a question the report can ask on its own.
typescript peer dependency is
installed; every other language is read as text, matched against what its frameworks
and its standard library define. The report states which of the two it did.unknown rather than a
guess.Every release from 0.3.3 onwards is published with npm provenance: an attestation, signed during the release workflow, that ties the tarball to the commit and the build that produced it.
npm view @produtype/core --json | grep -A5 provenance
Releases 0.3.0 to 0.3.2 have no attestation. They were published while this repository was private, and provenance is only meaningful when anyone can read the commit it points at.
Shipped: the deterministic analyzer, deterministic remediation planning, and the
optional AI layer as @produtype/ai.
Next: applying fixes as generated pull requests, and a hosted GitHub integration.
Deterministic CLI and library that analyzes a web application repository and reports how far it is from production-ready for the kind of product it is meant to be.
{ "mcpServers": { "produtype-core": { "command": "npx", "args": [ "-y", "@produtype/[email protected]" ] } }}टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
@produtype/core stdio पर लोकल चलता है।
पिछली जाँच 2026-10-28 को हुई। Deterministic CLI and library that analyzes a web application repository and reports how far it is from production-ready for the kind of product it is meant to be.