Agentpay MCP server

AgentPay MCP

AgentPay MCP is a stdio Model Context Protocol server for x402 payments and wallet operations. It exposes Agent Wallet SDK functions as MCP tools and loads a caller-controlled signing key from the local process environment.

The current npm package is agentpay-mcp v4.1.17.

Start without funds

Check the installed command without loading wallet credentials:

npx -y agentpay-mcp --version
npx -y agentpay-mcp --help

Use the AgentPay Wallet Starter for a no-funds verification of allowed, approval-required, and blocked policy outcomes.

MCP client configuration

Wallet tools read the following environment variables:

Example MCP configuration:

{
  "mcpServers": {
    "agentpay": {
      "command": "npx",
      "args": ["-y", "agentpay-mcp"],
      "env": {
        "AGENT_PRIVATE_KEY": "<secret-reference-or-local-key>",
        "AGENT_WALLET_ADDRESS": "0x<deployed-wallet-address>",
        "CHAIN_ID": "84532"
      }
    }
  }
}

Do not commit a real signing key. Use the client or operating system's secret mechanism where one exists. Start on Base Sepolia before using Base mainnet.

Tool groups

The tool registry in src/index.ts exposes these groups:

Tool schemas and handlers live under src/tools/.

Security boundaries

These boundaries matter more than the feature list:

viem for signing. Protect the process, environment, and MCP client config.

• The server reads AGENTPRIVATEKEY into its local Node.js process and uses

call that tool again, and a process restart clears its rolling state.

• setspendpolicy stores policy in the MCP server process. The same agent can

this is still application-level enforcement.

• Every current value-moving handler calls the in-process policy check, but

AgentAccountV2. setspendpolicy does not write those contract limits.

• On-chain limits exist only when the wallet owner configures them directly on

separate from the agent key.

• An over-limit transaction is a human gate only when the owner key is kept

request log and does not record rejected pre-chain attempts or read-only calls.

• gettransactionhistory reads on-chain wallet events. It is not an MCP

Sepolia. Unsupported chain IDs fail closed in src/utils/client.ts.

• Runtime wallet configuration currently supports Base mainnet and Base

with bounded values and independent wallet limits.

• Swap, bridge, escrow, and payment tools can move funds and consume gas. Test

Shortened. The full README is on GitHub.