specpack MCP server
online · 100% uptimeio.github.THE-KIPDEV/specpack·v0.1.0Audit and write CLAUDE.md / AGENTS.md / Cursor rules; generate full build specs for new projects.
0 stars50 downloads/wk
Reviews
Write oneNobody has reviewed specpack yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
specpack tools (5)
write = sends, deletes, buys or postsdraft_answersFreeAsks the server's AI (Claude) to fill the whole questionnaire from a plain-language project description; returns the project type, the answers and the assumptions it made. Takes 10-40 s and consumes one AI draft (3 free without an API key). Prefer answering get_questionnaire yourself when you already know the project; use this when you only have a one-line idea. Review the assumptions with the user before calling generate_spec.
generate_specFreeTurns questionnaire answers into a complete build specification (stack, database schema, auth flows, pages, design system, SEO, security, legal, deployment, file structure) and the matching agent files. Deterministic: the same answers always give the same bytes. Values: select/radio = one option value, multiselect = array of option values, boolean = true/false, number = number. Returns the requested files; by default AGENTS.md (full spec + working agreement) and CLAUDE.md (imports AGENTS.md) — write them at the repository root. Uses one spec from the quota (2 free without an API key).
get_questionnaireFreeThe questions for one project type: universal questions first, then type-specific ones. Each has an id, a type (text, textarea, select, radio, multiselect, boolean, number), options where relevant, and sometimes a condition (ask it only when another answer matches). Answer from what you know of the project, then pass the answers to generate_spec. Only project_name and project_description are required; skipped questions fall back to defaults.
get_usageFreeCurrent plan and quota usage (specs and AI drafts) for the API key, or for this address when no key is set.
list_project_typesFreeThe project types the spec generator knows (saas, ecommerce, business, marketplace, blog, webapp, landing), with what each covers.
Public scan report
scanner v0.1.10 · 2026-10-02 · same rubric, same numbers if you re-run it
- Code scan35 source files scanned25/25
- Live reliabilityremote reachable in 1368ms20/20
- Tool poisoning5 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 14 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How specpack compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 5
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 206 ms
- faster than 63% of 30,031 servers
- Downloads a week
- 50
- more than 42% of 12,191 servers with a package
What its tools let an agent do: 4 read · 1 create
Install specpack in Claude Code, Cursor or VS Code
claude mcp add --transport http specpack https://prompt-generator-website.com/mcp
What the publisher says
From the specpack repository's README, as published. We do not edit it. Read it on GitHub
specpack
Lint and generate the files your AI coding agent reads — CLAUDE.md, AGENTS.md, .cursorrules, Cursor rules — and turn a project description into a full build spec. CLI, library and MCP server.
npx specpack audit # bloat score for the agent files in this repo (offline)
npx specpack init # write a lean AGENTS.md from your manifests (offline)
npx specpack spec --describe "Booking app for dog groomers with deposits and SMS reminders"CLAUDE.md / AGENTS.md are loaded into the agent's context on every session. Every line that restates package.json, pastes a file tree or tells the model to "write clean code" costs tokens and competes with the two rules that actually matter. specpack audit finds those lines; specpack init starts you at the trimmed end.
Node ≥ 18. No account needed. audit and init never touch the network.
specpack audit — how much of your memory file does nothing?
Each line is classified keep, cut (removing it changes nothing: role-play preamble, generic advice, restated manifests, duplicates, emphasis inflation, prose) or offload (true but situational: file trees, schema dumps, endpoint lists, long code blocks, setup/deploy sections — move them to their own file and reference them with @docs/…). Same rules as the browser tool at prompt-generator-website.com/claude-md-audit.
Real output on a typical file:
$ npx specpack audit CLAUDE.md
CLAUDE.md 59% bloat · 44 lines · ~341 tokens every session
10 keep · 12 cut · 15 offload of 37 non-empty lines · ceiling 200, trimmed files land near 60
Over half of this file is doing nothing. It is not neutral weight — it is what your real rules are competing against.
3 cut You are an expert senior full-stack developer with 10 years of experience.
↳ role-play preamble: CLAUDE.md is project memory, not a system prompt. "You are an expert…" costs tokens and changes nothing about the code produced.
4 cut Please always write clean, readable and maintainable code.
↳ default behaviour: Removing this line does not make the model write worse code — it already tries to do this. It only dilutes the lines that matter.
5 cut IMPORTANT: follow best practices at all times.
…
12 cut - Next.js 15.1
↳ restates a manifest: package.json / composer.json / requirements.txt already state this, and the agent reads them. Keep it only if the version pin has a non-obvious reason.
…
18 offload ## Database schema
↳ situational section: Only a fraction of your sessions need this. Move tWithout arguments it audits every agent file in the current directory: CLAUDE.md, AGENTS.md, .cursorrules, .windsurfrules, .github/copilot-instructions.md, CLAUDE.local.md, .cursor/rules/*.mdc. - reads stdin.
In CI
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
specpack: common questions
- Is specpack MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the specpack safety report
- How do I install specpack?
- It runs remotely at prompt-generator-website.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does specpack need an API key?
- Yes. The registry entry asks for
SPECPACK_API_KEY,Authorization. - Is specpack maintained?
- The last commit was 47 days ago (2026-09-18). The latest release is v0.1.0.
- Is specpack up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does specpack compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.