Server facts
run402-mcp
Project
- Author
- MajorTal
- Repository
- github.com/MajorTal/run402-mcp
- Website
- run402.com
- License
- MIT
- Category
- Databases
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 24
- Last commit
- Data as of
Tags
- ai agent
- auth
- backend
- database
- mcp
- serverless
- storage
- supabase alternative
- x402
Overview
Postgres provisioning anchors run402-mcp, but its tools also cover the application resources surrounding a database. Agents using Claude Desktop, Cursor, Cline, or Claude Code can create projects, inspect schemas, execute SQL, and read or modify records through PostgREST. Authorization has a separate workflow: inspect the current exposure manifest, validate proposed rules without changing them, then apply declarations for tables, views, and database procedures. Undeclared tables remain inaccessible to anonymous and authenticated API users. Manifest validation can use migration SQL as reference material, but does not execute it or validate deployment specifications.
Application work can proceed through app_up or a structured deployment that combines migrations, authorization, functions, static files, route mappings, and secret declarations. Supporting tools upload assets, manage user authentication, configure mailboxes, and inspect deployment history, logs, and edge coherence. Snapshots provide internal recovery points, while contained branches support deployment rehearsals without altering the source project. Portable archives follow a distinct export, offline inspection, verification, and local import workflow; exported content excludes secrets and credentials. Billing tools expose tier status, balances, Stripe checkout, and x402 payments using USDC on Base.
run402-mcp setup notes
- run402-mcp records stdio only; confirm a network transport upstream before planning remote access.