Drain MCP Server

Pay for AI inference with USDC micropayments on Polygon. No API keys needed.

Local serverstdioTypeScript

What is the Drain MCP server?

Pay for AI inference with USDC micropayments on Polygon. No API keys needed. That is what the drain mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An open protocol for trustless, streaming micropayments between AI consumers and providers.

DRAIN enables permissionless, pay-per-token AI inference without intermediaries. Users open payment channels with USDC, stream requests to any compatible provider, and settle on-chain only when needed.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • Minimal — The protocol defines only what's necessary
  • Permissionless — Anyone can be a provider or consumer
  • Trustless — Cryptography replaces trust
  • Immutable — No admin keys, no upgrades, no fees
  • Problem — DRAIN Solution
  • Role — What They Do
  • Consumer — Pays for AI services
  • Provider — Delivers AI responses
  • Asset — Network
  • USDC — Polygon
  • Link — Description
  • URL — Purpose

What it needs from you

Configuration is passed through the environment: DRAIN_PRIVATE_KEY, OPENAI_API_KEY, PROVIDER_PRIVATE_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

drain-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Drain's toolset — Minimal, Permissionless, Trustless and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kimbo128; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Drain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
MinimalThe protocol defines only what's necessary
PermissionlessAnyone can be a provider or consumer
TrustlessCryptography replaces trust
ImmutableNo admin keys, no upgrades, no fees
ProblemDRAIN Solution
RoleWhat They Do
ConsumerPays for AI services
ProviderDelivers AI responses
AssetNetwork
USDCPolygon
LinkDescription
URLPurpose
ComponentDescription
PartyProtected Against

How to install the Drain MCP server

Configure in Cursor or Claude:

```json
{
  "mcpServers": {
    "drain": {
      "command": "npx",
      "args": ["-y", "drain-mcp"],
      "env": {
        "DRAIN_PRIVATE_KEY": "0x..."
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DRAIN_PRIVATE_KEYCredential the server authenticates with.Yes
OPENAI_API_KEYCredential the server authenticates with.Yes
PROVIDER_PRIVATE_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Drain to Minimal.
  • Use Drain to Permissionless.
  • Use Drain to Trustless.

Frequently asked questions

It connects Drain to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Minimal, Permissionless, Trustless, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Drain directly.