Skip to main content
Glama

ClawdPay MCP

Payments for AI Agents - An MCP server that enables Claude to make purchases using Privacy.com virtual cards.

npm version

Quick Start

npx clawdpay-mcp

Or install globally:

npm install -g clawdpay-mcp

Related MCP server: AgentCard MCP Server

Manual Setup

git clone https://github.com/Rishab87/clawdpay-mcp.git
cd clawdpay-mcp
npm install
npx playwright install chromium
npm run build

Configuration

Create .env file:

PRIVACY_API_KEY=your_key
PRIVACY_SANDBOX=true
HEADLESS=true

Claude Desktop Setup

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "clawdpay": {
      "command": "npx",
      "args": ["clawdpay-mcp"],
      "env": {
        "PRIVACY_API_KEY": "your_key",
        "PRIVACY_SANDBOX": "true"
      }
    }
  }
}

Tools

  • create_virtual_card: Create a single-use virtual card via Privacy.com

  • secure_auto_fill: Intelligently finds and fills payment fields on the current page

  • get_funding_sources: List available funding accounts

License

MIT

Available Tools

3 tools
create_virtual_cardC

Create a single-use virtual card via Privacy.com. Returns secure card details.

Inputs: merchant (required), amount_cents (required).

get_funding_sourcesB

List available funding accounts connected to Privacy.com

Inputs: no named parameters.

secure_auto_fillC

Intelligently finds and fills payment fields on the current page using robust heuristics.

Inputs: url (required), pan (required), cvv (required), exp_month (required), +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: create_virtual_card handles card creation, get_funding_sources lists funding accounts, and secure_auto_fill focuses on browser automation for payment fields. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency4/5

    Two tools follow a consistent verb_noun pattern (create_virtual_card, get_funding_sources), while secure_auto_fill uses a different adjective_noun style. This minor deviation slightly reduces consistency, but the names remain readable and descriptive overall.

    Tool Count3/5

    With only 3 tools, the server feels thin for a payment integration domain, which typically involves more operations like updating cards, managing transactions, or handling errors. While the tools cover basic needs, the scope seems limited compared to what might be expected.

    Completeness2/5

    The toolset has significant gaps for a payment integration server. It lacks essential operations such as updating or deleting virtual cards, viewing transaction history, managing card limits, or handling errors. This incomplete surface will likely cause agent failures in common payment workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage and use prepaid virtual Visa cards with hard budget limits for secure online transactions. It provides tools for creating cards, checking balances, and retrieving payment credentials with human-in-the-loop approvals.
      1
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to make payments and manage subscriptions by converting USDC stablecoin balances into virtual cards for online checkouts. It provides tools for wallet management, card issuance, and secure transaction handling through the Clawallex payment API.
      18
      54 npm
      -