# Run402 [Health: Active]

**Category:** 🗄️ Databases  
**Repository:** https://github.com/kychee-com/run402  
**GitHub Stars:** 24  
**npm Downloads (last month):** 21390  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/run402

## Description
x402 pay-per-call infra for agents: $0.03 image generation, Postgres, auth, storage, functions.

## Tools
Capabilities this server exposes over MCP:

- **up** — The first deploy: any missing setup (wallet, tier, project, workspace link), then the deploy. Returns the `run402.up.result` envelope.
- **deploy** — Applies a ReleaseSpec to a project (`r.project(id).apply`): database, functions, site, `site.public_paths`, assets, subdomains, `routes.replace`. Returns the `DeployResult`.
- **status** — r.status()`: the wallet the server acts as (`local_label`, `server_label`, address), tier and lease, allowance, projects, active project.
- **whoami** — r.orgs.whoami()`: the remote principal, its authenticators, org memberships, and sign-in session grade.
- **doctor** — r.doctor()`: `{ ok, blocking[], warnings[], checks[] }`.
- **docs** — The SDK reference and the `run` primer, shipped in the package: `topic` (a namespace or section) or `search`.
- **run** — Runs a TypeScript snippet against the SDK in a sandbox; returns the value, the captured logs, and the SDK calls it made.
- **expand_result** — Pages a stored result: a `run` value or its logs, a `docs` answer, `up`'s detail.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What Run402 MCP server does

Run402 MCP server exposes the agent-facing operations of Run402 through Model Context Protocol. It is intended for hosts such as Claude Desktop, Cursor, Cline, and Claude Code that need to provision and manage backend resources through tool calls.

The underlying platform combines a Postgres database, REST API, user authentication, content-addressed file storage, static site hosting, serverless functions, and image generation. Deployments are paid through Run402’s supported payment flows, including x402 with USDC on Base, MPP with pathUSD on Tempo or sats over Bitcoin Lightning, and card-funded allowance. The prototype tier runs on testnet.

## How it works

The MCP package acts as a thin interface over Run402’s typed SDK. `up` handles first-time preparation and deployment in one operation, creating or linking the required wallet, tier, project, and workspace state before applying the deployment. `deploy` applies a `ReleaseSpec` to an existing project, including database changes, functions, sites, assets, subdomains, public site paths, and route replacements.

Account and environment inspection are separate operations. `status` reports the wallet identity used by the server, tier and lease information, allowance, projects, and active project. `whoami` returns the remote principal, authenticators, organization memberships, and sign-in session grade. `doctor` produces an overall result with blocking issues, warnings, and individual checks.

The `run` tool executes a TypeScript snippet against the SDK in a sandbox. Its response includes the returned value, captured logs, and SDK calls made during execution. This provides access to SDK workflows that do not have a dedicated MCP tool. Results that are too large for one response can be retrieved with `expand_result`, which pages stored values from `run`, logs, documentation answers, or deployment details.

## Setup and configuration

Run402 is distributed as an MCP package and is designed for MCP-native hosts. The repository identifies Claude Desktop, Cursor, Cline, and Claude Code as supported surfaces. Run402’s broader interface also includes a CLI and typed SDK, but those are separate ways to use the platform rather than additional MCP tools.

The platform’s normal workflow starts with a project manifest and a site entry point such as `index.html`, then uses `up` to bootstrap the missing prerequisites and deploy. The CLI documentation recommends `run402 up --name ... -y` for an initial deployment; MCP callers can use the corresponding `up` operation.

## Tools and capabilities

- `up`: Completes missing wallet, tier, project, and workspace-link setup, then deploys.
- `deploy`: Applies a release specification covering backend, site, asset, subdomain, and route changes.
- `status`: Inspects the server wallet, account allowance, tier, lease, projects, and active project.
- `whoami`: Inspects the remote principal, authenticators, memberships, and session grade.
- `doctor`: Runs diagnostics and separates blocking findings from warnings and checks.
- `docs`: Searches or retrieves the bundled SDK reference and `run` primer by topic or search term.
- `run`: Executes TypeScript against the SDK and returns its value, logs, and recorded SDK calls.
- `expand_result`: Pages stored deployment, execution, log, or documentation results.

## Limitations and notes

MCP result details may be retained for later retrieval through `expand_result`, rather than returned in one response. The SDK retains full results for typed callers, while CLI diagnostics are written in redacted form under `.run402/diagnostics/`.

Run402 uses principal-based identity and explicit authority. Organization memberships, roles, grants, grant keys, freshness, and spending policy affect what an acting principal can do. The platform is open source at the agent-surface level under MIT; its self-hostable runtime slice is maintained separately under Apache-2.0, while the managed Cloud control plane is proprietary.

_Full upstream README: https://allmcps.com/mcp/run402/readme_