Pocketlantern MCP server

by pocketlantern·io.github.pocketlantern/pocketlantern·v0.2.0·4 stars

No reviews yet

Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.

B74/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B74/100

full report

Adoption

New

4 stars47 downloads/wk

Reviews

Write one

Nobody has reviewed Pocketlantern yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Pocketlantern tools (8)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

get_card
Get the full content of a technology decision card by ID. Returns all candidate solutions with tradeoffs, cautions, and official reference links. Use after search_cards to deep-dive into a specific decision.
get_cards
Get full content of multiple cards by IDs in one call (max 5). Use instead of calling get_card repeatedly when you need to compare several candidates side by side.
get_related_cards
Get summaries of cards related to a given card. Use after reading a card to explore connected technology decisions (e.g. auth → OAuth flows → password hashing).
list_categories
List available topic categories (auth, backend, database, frontend, infra, testing) with card counts. Call this first to understand what technology decisions are covered.
list_constraints
List environment constraints (serverless, enterprise, small-team, etc.) that can filter search results. Use when you know the project's environment and want only relevant cards.
list_tags
List all searchable tags with counts, optionally filtered by category. Use to discover available topics and refine search queries.
report_issue
Report a quality issue with PocketLantern cards. Use when: a topic has no card ('no_card'), a card has wrong facts ('inaccurate'), info seems outdated ('stale'), or the correct answer differs from the card ('answer_changed').
search_cards
Before finalizing answers about technology choices, upgrades, migrations, licensing, or vendor selection — check this tool for blockers in these bundled decision cards. Your training data may be stale. Returns source-linked decision cards as of this bundle — surfacing EOL dates, breaking changes, version floors, lock-in risks (password export, vendor dependency), pricing model changes, and migrati

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings

Code scan37 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 184 days ago4/15
Maintainer identityregistry namespace matches repository owner7/10

Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Pocketlantern compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 74/100; higher than 40% of 48,255 servers
Tools: 8; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 4; more than 82% of 28,688 servers
Downloads a week: 47; more than 39% of 12,191 servers with a package

What its tools let an agent do: 8 read

Install Pocketlantern in Claude Code, Cursor or VS Code

Runs npx -y @pocketlantern/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pocketlantern -- npx -y @pocketlantern/mcp-server

Add to Cursor

What the publisher says

From the Pocketlantern repository's README, as published. We do not edit it. Read it on GitHub

PocketLantern

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.

Try these queries

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.

Quick start

Prerequisites: Node.js >= 22, an MCP client (Claude Code, Cursor, etc.)

npm install -g pocketlantern

Claude Code

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.

Cursor / Windsurf / other MCP clients

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.

More queries to try

Billing split to Active CPU + Memory, shared-process concurrency breaks isolation

"How did Vercel pricing change with Fluid Compute?"

Prisma v7 ESM + driver adapter breaking, Edge preview-only; Drizzle 0.30-1.0 also breaking

"Prisma or Drizzle for Edge/serverless?"

Verify installation

pocketlantern doctor               # check installation status
pocketlantern search "auth pricing" # search cards from CLI

How it works

PocketLantern is an MCP server. Your AI agent calls searchcards — 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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Pocketlantern: common questions

Is Pocketlantern MCP server safe?: Mostly: it is graded B (74/100). Read the Pocketlantern safety report
How do I install Pocketlantern?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Pocketlantern need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Pocketlantern maintained?: The last commit was 222 days ago (2026-03-27). The latest release is v0.2.0.
What can I use instead of Pocketlantern?: Servers from other publishers that do the same job: State Memory MCP server.
How does Pocketlantern compare with other MCP servers?: safety score 74/100 (higher than 40% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Pocketlantern

Same job from other publishers: the closest match first, then the best rated.

State Memory MCP
Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
not reviewed
Established
A