Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pocketlantern": {
"command": "npx",
"args": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
}Run this in your terminal
claude mcp add pocketlantern -- npx -y @pocketlantern/mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pocketlantern": {
"command": "npx",
"args": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pocketlantern": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pocketlantern/mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account pocketlantern, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Your AI agent sounds confident. It missed the blockers.
Prices shift, versions break, licenses change. PocketLantern is a blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.
Ask your AI agent after installing PocketLantern:
"Which auth provider — Clerk, Auth0, or Cognito?"
⚠️ Cognito password hashes are permanently non-exportable
⚠️ Auth0 password export requires support ticket — Free tier excluded ⚠️ Auth0 Rules/Hooks EOL 2026-11-18 — Actions not portable ✅ Clerk has the most flexible migration path
"Should I upgrade to Next.js 16?"
⚠️ Sync API access fully removed — all dynamic calls must be awaited
⚠️ Custom webpack config breaks next build ⚠️ next lint removed — switch to Biome or ESLint CLI ⚠️ Requires Node.js 20.9.0+, TypeScript 5.1.0+, React 19.0+ ✅ Plan phased migration — codemod doesn't cover webpack or middleware
"Can I use the OpenAI Realtime API?"
⚠️ gpt-4o-realtime-preview removed 2026-05-07
⚠️ Beta interface (realtime=v1 header) removed same date ⚠️ GA event schema incompatible — 4 event renames ✅ Start on GA from day one — or plan dual-stack migration
Three questions. Three blocker types. Same AI, different facts.
Prerequisites: Node.js >= 22, an MCP client (Claude Code, Cursor, etc.)
npm install -g pocketlantern
In your project directory:
cd your-project
pocketlantern init
init registers the MCP server in ~/.claude.json and adds a one-line rule to your project's CLAUDE.md. Restart Claude Code (Ctrl+C, then run claude again), then ask your first query.
Add to your MCP config (Cursor: ~/.cursor/mcp.json):
{
"mcpServers": { "pocketlantern": { "command": "pocketlantern-mcp" } } }
Then add this line to your project rules (.cursorrules, Kiro steering file, etc.):
For technology decisions, upgrades, migrations, or licensing questions: before finalizing your answer, check the PocketLantern MCP server's search_cards tool for blockers in these bundled decision cards — your training data may be stale.
Reload MCP servers: Cursor — Cmd+Shift+P -> "MCP: Restart Servers". Windsurf — restart the editor.
pocketlantern doctor # check installation status
pocketlantern search "auth pricing" # search cards from CLI
PocketLantern is an MCP server. Your AI agent calls search_cards — and gets source-linked decision cards plus source-linked blocker warnings where available.
Agent asks question
-> search_cards("clerk vs auth0 authentication") -> 3 cards + 5 blocker warnings (lock-in, EOL, export restrictions) -> Agent answers with source-linked constraints
Local cardset. Instant lookup. No vector database. No embeddings. Keyword search, card links, and source-linked blocker warnings where available. The value is in source-linked decision cards, not clever retrieval alone.
search_cards("auth", constraints:["serverless"]) -> cards + blockers
get_card("auth/clerk-vs-auth0-vs-cognito-2026") -> full card with facts get_related_cards(...) -> connected topics
Blocker-aware decision cards across 27 categories — plus source-linked blocker warnings from the bundled graph index. Ships with the npm package, works immediately, no network, no account:
| Category | What it covers |
|---|---|
| auth | Vendor lock-in, migration pain, SSO, RBAC, passkeys |
| frontend | Next.js, React, Svelte, Vite, Angular upgrade blockers |
| database | Prisma, Drizzle, Postgres, Aurora, Neon, Supabase |
| ai | OpenAI API migrations, model pricing, batch vs streaming |
| serverless | Vercel, Cloudflare Workers, Lambda cost and runtime |
| infra | Hosting platforms, Terraform, Node.js LTS, Python EOL |
| backend | Supabase vs Firebase, Express, job queues, realtime sync |
| + 18 more | deployment, devtools, testing, security, compliance, ... |
Each card is a structured YAML file with source-linked facts and official reference links:
id: auth/clerk-vs-auth0-vs-cognito-2026
title: Clerk vs Auth0 vs Cognito Under Current Pricing and Feature Changes problem: Select an auth vendor given recent pricing shifts, MAU economics, ... constraints: [cost-sensitive, low-ops, enterprise, compliance, serverless] candidates:
tags: [auth, clerk, auth0, pricing, passkeys, b2b, compliance] related_cards: [auth/sso-for-b2b-saas, auth/rbac-vs-abac-vs-rebac] updated: 2026-03-14
See packages/schema/src/card.ts for the full schema definition.
pocketlantern/
packages/schema/ <- Card schema (zod + TypeScript types) apps/mcp-server/ <- MCP server (search, retrieval, tool handlers) apps/cli/ <- CLI (validate, search, init, doctor) packages/knowledge/ <- Decision cards + graph index (data package) docs/ <- User guides & roadmap
Monorepo: pnpm workspace. Build order: schema -> knowledge (no build) -> mcp-server -> cli.
pnpm build # Build all packages
pnpm test # Run tests (299 tests) pnpm test:coverage # Run with coverage report pnpm lint # ESLint pnpm format:check # Prettier check
Missing a topic? Request coverage in Card Requests.
Contributions to the tool (schema, MCP server, CLI, search) are welcome. See CONTRIBUTING.md for guidelines.
MIT