PayRouter

PayRouter

Universal agentic payment router that gives AI agents the ability to pay across multiple payment rails through a single MCP interface, with cross-rail budget enforcement and a unified audit trail.

Category
访问服务器

README

PayRouter

Universal agentic payment router. One MCP server, every payment rail.

PayRouter gives any AI agent — Claude, ChatGPT, Cursor, or custom — the ability to pay across multiple payment rails through a single interface, with cross-rail budget enforcement and a unified audit trail.

What it does

┌─────────────────────────────────────────────┐
│              PayRouter Server               │
│                                             │
│   MCP Endpoint    REST API    Dashboard     │
│   /mcp            /api/v1/*   :3000         │
│                                             │
│   ┌─────────────────────────────────────┐   │
│   │         Core Engine                 │   │
│   │  Mandate Engine → Router → Adapter  │   │
│   └─────────────────────────────────────┘   │
│       │         │        │         │        │
│     x402    Lightning  Stripe     UPI       │
│   (USDC)    (BTC/LN)  (Card)   (INR)       │
└─────────────────────────────────────────────┘
  • MCP server (Streamable HTTP) — any MCP client connects and gets payment tools
  • Mandate engine — cross-rail budget limits, category/merchant restrictions, deny-by-default
  • Smart routing — picks the best rail, falls back on failure
  • Dashboard — live transactions, budget bars, rail config, setup wizard
  • Docs site — Fumadocs + Next 16, Stripe-like documentation

Supported rails

Rail Protocol Currency Status
x402 HTTP 402 + stablecoins USDC on Base Working
Lightning L402 + NWC BTC (sats) Working (see examples/l402)
Stripe Shared Payment Tokens USD/EUR/GBP Planned
UPI Reserve Pay (Razorpay) INR Planned

Quick start

git clone https://github.com/ram0verflow/payrouter.git
cd payrouter
nvm use          # Node 22
pnpm install
pnpm -r build
pnpm --filter @payrouter/server start

If no rails are configured, the setup wizard opens at http://localhost:3000/setup.

Connect an agent

Add to your Claude Desktop config:

{
  "mcpServers": {
    "payrouter": {
      "url": "http://localhost:3001/mcp"
    }
  }
}

The agent gets 5 tools: request_payment, check_budget, list_transactions, discover_merchant_rails, revoke_all.

MCP tools

request_payment

merchant: "https://api.example.com"
amount: 0.01
currency: "USD"
preferred_rail: "auto"

Checks mandate → routes to best rail → executes payment → returns normalized receipt.

check_budget

Returns remaining budget across all rails for the current agent.

list_transactions

Recent transaction history with rail/category/date filters.

discover_merchant_rails

Probes a URL to detect which payment rails the merchant accepts (HTTP 402 headers, etc).

revoke_all

Emergency kill switch — revokes all payment capabilities immediately.

Project structure

payrouter/
├── packages/
│   ├── core/              # Mandate engine, router, receipt schema, types
│   ├── adapters/
│   │   └── x402/          # x402 stablecoin adapter
│   └── server/            # MCP + REST API + SQLite
├── apps/
│   ├── dashboard/         # React + Vite + Tailwind
│   └── docs/              # Fumadocs + Next 16
├── examples/
│   └── l402/              # L402 Lightning payment example (testnet)

Configuration

Create payrouter.config.json or use the dashboard setup wizard:

{
  "server": {
    "port": 3001,
    "dashboard_port": 3000,
    "db_path": "./payrouter.db"
  },
  "rails": {
    "x402": {
      "enabled": true,
      "wallet_private_key": "0x...",
      "network": "base-sepolia"
    }
  },
  "mandates": {
    "default": {
      "daily_limit": 100,
      "per_transaction_limit": 50,
      "allowed_categories": ["*"],
      "allowed_merchants": ["*"]
    }
  }
}

Environment variables also work — see .env.example.

Development

pnpm --filter @payrouter/server start    # API server on :3001
pnpm --filter dashboard dev              # Dashboard on :3000
pnpm --filter docs dev                   # Docs on :3002

Tech stack

  • TypeScript, pnpm workspaces
  • MCP: @modelcontextprotocol/sdk (Streamable HTTP)
  • Database: better-sqlite3
  • x402: @x402/fetch + @x402/evm + viem
  • Lightning: @getalby/sdk (NWC)
  • Dashboard: React 19 + Vite + Tailwind CSS
  • Docs: Fumadocs + Next.js 16 + Turbopack

License

MIT

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选