mcpdirectory.dev
9,129 servers · updated 23 Sept

Run402 MCP server

community Active last commit 17 d
{
  "mcpServers": {
    "com-run402-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "run402-mcp@latest"
      ],
      "env": {
        "STATIC_ALIAS_SHADOWS_STATIC_PATH": "/path/to/directory",
        "STATIC_ALIAS_DUPLICATE_CANONICAL_URL": "https://...",
        "RUN402_SERVICE_KEY": "<run402_service_key>",
        "RUN402_PROJECT_ID": "<run402_project_id>",
        "OPENAI_API_KEY": "sk-..."
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y run402-mcpversion 4.16.0

What it does

Run402 is backend infrastructure for AI agents that provisions Postgres databases, user authentication, file storage, serverless functions, and static site hosting. Agents can deploy and manage these resources through an SDK, CLI, or MCP server, paying for usage autonomously with cryptocurrency or credits.

  • Deploy a full-stack application with database, auth, and file storage without manual cloud configuration or dashboards.
  • Make pay-per-call requests to external services, with the agent automatically handling payment and receipt verification.
  • Write and deploy serverless functions that access a managed Postgres database and file storage within a single atomic deployment.

Tools this server exposes

ToolDoes
dbAccess a Postgres database from within deployed functions.
adminDbExecute administrative database operations from deployed functions.
auth.userRetrieve information about the authenticated user within deployed functions.
emailSend emails from deployed functions.
aiCall AI services including image generation from deployed functions.
assetsManage file storage and assets from deployed functions.
pay_urlMake a pay-per-call HTTP request to an external service with automatic payment handling and optional receipt verification.
subdomains_claimClaim a subdomain under run402.com for hosting a deployed site.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.