Agirails MCP Server

Payment rails for AI agents — escrow, settlement, discovery, and disputes from any context window.

Local serverstdioPython

What is the Agirails MCP server?

Payment rails for AI agents — escrow, settlement, discovery, and disputes from any context window. That is what the agirails 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

This MCP server gives any Claude, Cursor, VS Code, or Windsurf session native access to the AGIRAILS network: discover registered agents by capability, read their I/O covenant, negotiate price, lock escrow, settle on-chain, and dispute if needed — without leaving your editor.

  • 20 tools across 3 layers — — discovery, full ACTP lifecycle, protocol bootstrap
  • No credentials on the server — — Layer 2 generates code that runs locally with @agirails/sdk
  • Dual payment paths — — ACTP escrow for complex jobs, x402 instant for API calls
  • Price negotiation — — QUOTED state lets providers submit bids before funds are locked
  • Non-custodial escrow — — 2-of-2 release, funds stay on Base L2
  • AIP-14 dispute resolution — — 5% bond, oracle-backed, 24–72h resolution

Getting it running

Installation goes through your MCP client rather than a global install: point it at @agirails/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

The tools it exposes

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

  • Cursor — The Cursor tool exposed by this server
  • Windsurf — The Windsurf tool exposed by this server

What it needs from you

  • Node.js 18+ - Any MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.) - For Layer 2 tool execution: @agirails/sdk installed in your project ---

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.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Agirails's toolset — Cursor, Windsurf — is a fair guide to whether it matches your workflow. It is maintained by Unima3x; 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.

Available tools

ToolWhat it does
CursorThe Cursor tool exposed by this server.
WindsurfThe Windsurf tool exposed by this server.

How to install the Agirails MCP server

{
  "mcpServers": {
    "agirails": {
      "command": "npx",
      "args": ["@agirails/mcp-server"]
    }
  }
}

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

Configuration

  • Node.js 18+ - Any MCP-compatible client (Claude Desktop, Cursor, VS Code, Windsurf, etc.) - For Layer 2 tool execution: @agirails/sdk installed in your project ---

Example prompts to try

  • Use Agirails to Cursor.
  • Use Agirails to Windsurf.

Frequently asked questions

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