Run402 — Claude Code MCP server: backend built for agents
Lets an agent spin up Postgres, auth, files, functions and hosting on its own. Usage is paid per call with x402 or MPP.
claude mcp add --transport http mcp https://mcp.run402.com/mcpWhat Run402 does
Run402 is an open backend that speaks to a machine rather than a person. Through MCP tools an agent sets up a Postgres database, user auth, content-addressed storage and serverless functions, then ships the whole thing in one staged deploy. No dashboard login is needed to begin, and there is no API key to copy by hand.
Billing works from a wallet: x402 with USDC on Base, MPP with pathUSD on Tempo, or sats over Bitcoin Lightning. A card-funded allowance is another route. The prototype tier is free on testnet, which is a sensible place to find out whether the workflow fits you. Each MCP tool is a thin wrapper over a call in @run402/sdk; the same operations exist in the CLI and in TypeScript.
The remote endpoint at https://mcp.run402.com/mcp runs over HTTP. If you start the server locally with npx -y run402-mcp, set RUN402_WALLET — skip it and the agent has nothing to pay with, so payment fails. The MCP surface is narrower than the CLI: for scripts and CI, reach for run402 on the command line. Tool output arrives trimmed, and expand_result opens the detail behind it.
What it helps with
- provision a Postgres database and REST API from the agent
- pay for service calls straight from an agent wallet
- ship a static site and functions with staged deploys
- attach content-addressed file storage to a project
- re-verify an app over HTTP without a fresh deploy
Example prompts for the agent
- Bootstrap a run402 project named
my-appand deploy this folder - List the run402 functions deployed in this project
- Re-check the app's HTTP responses on staging
How to install Run402
1Platform CLI: remote server
claude mcp add --transport http mcp https://mcp.run402.com/mcp2Platform CLI
claude mcp add --env RUN402_WALLET=<RUN402_WALLET> --transport stdio run402 -- npx -y run402-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add run402 --url https://mcp.run402.com/mcp2Platform CLI
codex mcp add run402 --env RUN402_WALLET=<RUN402_WALLET> -- npx -y run402-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"run402": {
"url": "https://mcp.run402.com/mcp"
}
}
}{
"mcpServers": {
"run402": {
"command": "npx",
"args": [
"-y",
"run402-mcp"
],
"env": {
"RUN402_WALLET": "<RUN402_WALLET>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"run402": {
"type": "http",
"url": "https://mcp.run402.com/mcp"
}
}
}{
"servers": {
"run402": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"run402-mcp"
],
"env": {
"RUN402_WALLET": "<RUN402_WALLET>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http run402 https://mcp.run402.com/mcp2Platform CLI
gemini mcp add -e RUN402_WALLET=<RUN402_WALLET> run402 npx -y run402-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Run402
How do I install Run402 in Claude Code?
Add the HTTP transport with claude mcp add --transport http run402 https://mcp.run402.com/mcp. For a stdio setup, run claude mcp add --env RUN402_WALLET=<RUN402_WALLET> --transport stdio run402 -- npx -y run402-mcp, replacing the placeholder with your wallet.
What does Run402 do?
It hands an agent a full backend: Postgres, auth, file storage, static hosting, serverless functions and image generation. Provisioning, deploys and payment flow through the CLI, the SDK or MCP.
How is payment handled?
Agents settle through x402 in USDC on Base, MPP in pathUSD on Tempo, or sats over Bitcoin Lightning. A card-funded allowance covers the other case.
