Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts
Blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts. That is what the pocketlantern mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Prices shift, versions break, licenses change. PocketLantern is a blocker-aware decision layer for AI coding agents, grounded in source-linked, time-sensitive facts.
The server publishes 8 tools. What each one is for:
name — ClerkCategory — What it coversauth — Vendor lock-in, migration pain, SSO, RBAC, passkeysfrontend — Next.js, React, Svelte, Vite, Angular upgrade blockersdatabase — Prisma, Drizzle, Postgres, Aurora, Neon, Supabaseserverless — Vercel, Cloudflare Workers, Lambda cost and runtimeinfra — Hosting platforms, Terraform, Node.js LTS, Python EOLbackend — Supabase vs Firebase, Express, job queues, realtime syncThe server ships on npm as pocketlantern, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pocketlantern's toolset — name, Category, auth and 5 more — is a fair guide to whether it matches your workflow. It is maintained by pocketlantern; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pocketlantern's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| name | Clerk |
| 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 |
| 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 |
{
"mcpServers": {
"pocketlantern": {
"command": "npx",
"args": ["-y", "pocketlantern"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.