MCP server for Run402 — pay-per-call infrastructure for AI agents over x402 USDC micropayments. Generate an image for $0.03 with no signup, or
Run402 MCP server exists for a simple reason — assistants are far more useful when they can act on Run402 directly instead of describing what you should do. MCP server for Run402 — pay-per-call infrastructure for AI agents over x402 USDC micropayments. Generate an image for $0.03 with no signup, or provision Postgres databases with REST API, auth, storage and row-level security.
Once Run402 is connected, these are the calls the assistant has available:
Surface — Use when…You will need 4 environment variables: RUN402_PROJECT_ID, OPENAI_API_KEY, STATIC_ALIAS_SHADOWS_STATIC_PATH, STATIC_ALIAS_DUPLICATE_CANONICAL_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Run402's toolset — Surface — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Surface | Use when… |
{
"mcpServers": {
"run402": {
"command": "npx",
"args": ["-y", "run402"],
"env": {
"RUN402_PROJECT_ID": "your-value",
"OPENAI_API_KEY": "your-value",
"STATIC_ALIAS_SHADOWS_STATIC_PATH": "your-value",
"STATIC_ALIAS_DUPLICATE_CANONICAL_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| RUN402_PROJECT_ID | Configuration value read at startup. | Optional |
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| STATIC_ALIAS_SHADOWS_STATIC_PATH | Filesystem location the server is allowed to use. | Optional |
| STATIC_ALIAS_DUPLICATE_CANONICAL_URL | Endpoint or connection string the server talks to. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.