Offline MCP server for planning structured project specs — validate, render, and checklist tools.
MCPpedia last refreshed this data
io.github.rbsoftwaresystems/draftlytic-mcp is an MCP server that offline MCP server for planning structured project specs — validate, render, and checklist tools. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 79/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"draftlytic": {
"args": [
"-y",
"draftlytic-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Offline MCP server for planning structured project specs — validate, render, and checklist tools.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'draftlytic-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked draftlytic-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
Private-by-default, local-first memory/context/task orchestrator for MCP apps and agents.
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
SQL for Android APK and DEX files: classes, methods, strings, references and smali.
System 1 decision models (Jev, Laya, Cua-S1) as brain for agents: Browser use, computer use, games and robotics
MCP Security Weekly
Get CVE alerts and security updates for io.github.rbsoftwaresystems/draftlytic-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that turns a rough project idea into a structured spec — right inside Claude Code, Cursor, or any MCP-compatible editor. No API key, no account, no network calls. It runs entirely on your machine and hands your editor's model a schema to write into, a checklist of what to ask about, a validator that catches gaps before you start coding, and a renderer that turns the result into a clean Markdown PRD.
This exists because "vibe coding" from a one-line prompt tends to produce a plausible-looking app that's missing half the decisions you actually needed to make — what's in scope for v1, what the data model looks like, what "done" means for a feature. draftlytic-mcp doesn't generate any of that for you; it structures the conversation so your model asks the right questions, then checks its own homework before you start building.
claude mcp add draftlytic -- npx -y draftlytic-mcp
Add to .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):
{
"mcpServers": {
"draftlytic": {
"command": "npx",
"args": ["-y", "draftlytic-mcp"]
}
}
}
Most MCP hosts read a generic mcp.json with the same shape:
{
"mcpServers": {
"draftlytic": {
"command": "npx",
"args": ["-y", "draftlytic-mcp"]
}
}
}
Once connected, ask your editor's model something like:
Use the plan_project prompt for "a habit tracker that reminds me by text message"
It'll walk through spec_checklist with you (platform, tech stack, audience, features, competitors, revenue, constraints, data model, notifications, external services, design & UX — a handful of concrete questions per category, many offered as click-to-pick single/multi-select choices rather than blank prompts, with a free-text escape always available), draft a spec, run it through validate_spec, fix what comes back, and hand you a rendered PRD in Markdown you can drop straight into a coding-agent prompt, a SPEC.md, or a GitHub issue.
You can also call the tools directly if you already have a spec drafted (by hand, or from another source) and just want it checked and rendered.
| Tool | Input | What it does |
|---|---|---|
validate_spec | spec (JSON object) | Zod-validates the spec and returns structured issues: errors for missing/empty required sections, placeholder text (TBD, lorem ipsum, fixme, etc.), and features without a priority — plus non-blocking quality hints like "no acceptance criteria on your must-haves" or "no non_goals listed". |
render_prd | spec (JSON object) | Renders a validated spec into deterministic Markdown: title, overview, target audience, platforms, tech stack, features grouped by priority with acceptance-criteria checklists, screens & navigation, data model tables, constraints, and non-goals. Refuses to render (returns an error) if the spec h |