@everystack/mcp

MCP server that makes Claude an everystack expert. Provides architecture knowledge, project introspection tools, and guided workflow prompts so Claude can help build apps from V1 (static) to V3 (full platform).

Setup

Add to your project's .mcp.json:

{
  "mcpServers": {
    "everystack": {
      "command": "npx",
      "args": ["@everystack/mcp"]
    }
  }
}

Or for a monorepo workspace:

{
  "mcpServers": {
    "everystack": {
      "command": "npx",
      "args": ["tsx", "packages/mcp/src/index.ts"]
    }
  }
}

What It Provides

Resources (Knowledge)

Claude reads these to understand everystack architecture and conventions.

Core (loaded first):

• everystack://core — Architecture, package map, tiers, conventions, handler reference
• everystack://security — Three-layer security model, AWS IAM profiles, RLS policies

Detail (loaded on demand):

• everystack://handler-options — Complete createHandler() options reference
• everystack://query-protocol — PostgREST filter syntax, embedding, aggregates
• everystack://client-api — Typed client, query builder, mutations
• everystack://auth — JWT auth flows, OAuth, token lifecycle
• everystack://schema-patterns — Drizzle schema design, migrations, RLS
• everystack://deployment — SST config, secrets, stages, resource linking
• everystack://admin — Declarative admin dashboard
• everystack://jobs — SQS background workers
• everystack://storage — S3 file uploads, presigned URLs
• everystack://logging — Structured logging, crash reports, analytics
• everystack://security-device — Device attestation, biometric auth
• everystack://testing — Jest setup, TDD workflow, mocking patterns
• everystack://plugins — Plugin system for composing handlers
• everystack://ssr — Server-side rendering, loaders, SEO
• everystack://images — Sharp image processing, CDN delivery
• everystack://events — Real-time events via LISTEN/NOTIFY + WebSocket
• everystack://cli — CLI command reference

Tools (Project Introspection)

Read-only tools that analyze your project and return structured data.

| Tool | Purpose | |------|---------| | project_status | Detect tier (V1/V2/V3), installed packages, project structure, deployment state | | schema_analyze | Parse Drizzle schema, cross-reference handler config, detect misconfigurations | | project_validate | Check for security gaps, missing dependencies, convention violations |

Prompts (Guided Workflows)

Structured prompts that guide Claude through multi-step tasks.

| Prompt | Purpose | |--------|---------| | new-app | Scaffold a new everystack app (V1/V2/V3) | | add-feature | Add auth, jobs, storage, images, admin, logging, security, SSR, or events | | design-schema | Plain English → Drizzle schema + RLS policies + handler config | | deploy | Stage-specific deployment walkthrough | | debug | Systematic debugging based on symptoms | | secure | AWS IAM profiles + RLS + JWT auth setup |

Design

Standalone. Zero everystack peer dependencies. Only depends on @modelcontextprotocol/sdk and zod. Works even when the project is broken or partially set up.

Local-only. Runs via stdio transport. No network access, no AWS calls. The everystack CLI handles remote infrastructure — the MCP teaches Claude how to use it.

Read-only tools. Tools read files and return structured data. Claude does the reasoning. No file writes, no imports from other packages.

Curated resources. The markdown files are optimized for Claude consumption — organized by task, not by package. Each follows a consistent structure: When to Use, Setup, API Reference, Common Patterns, Gotchas.

Development

pnpm --filter @everystack/mcp test     # Run tests (58 passing)
pnpm --filter @everystack/mcp lint     # Type check