run402-mcp

MCP server for Run402 — provision and manage AI-native Postgres databases from any MCP-compatible client.

Quick Start

npx run402-mcp

Tools

Client Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "run402": {
      "command": "npx",
      "args": ["-y", "run402-mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "run402": {
      "command": "npx",
      "args": ["-y", "run402-mcp"]
    }
  }
}

Cline

Add to Cline MCP settings:

{
  "mcpServers": {
    "run402": {
      "command": "npx",
      "args": ["-y", "run402-mcp"]
    }
  }
}

Claude Code

claude mcp add run402 -- npx -y run402-mcp

How It Works

1. Provision — Call provision_postgres_project to create a database. The server handles x402 payment negotiation and stores credentials locally.
2. Build — Use run_sql to create tables, rest_query to insert/query data, and upload_file for storage.
3. Renew — Call renew_project before your lease expires.

Payment Flow

Provisioning and renewing require x402 micropayments. When payment is needed, tools return payment details (not errors) so the LLM can reason about them and guide the user through payment.

Key Storage

Project credentials are saved to ~/.config/run402/projects.json with 0600 permissions. Each project stores:

• anon_key — for public-facing queries (respects RLS)
• service_key — for admin operations (bypasses RLS)
• tier — prototype, hobby, or team
• expires_at — lease expiration timestamp

Environment Variables

Development

npm run build
npm run test:skill

License

MIT