Skip to main content
Glama
README.md
# ClawdPay MCP

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

[![npm version](https://badge.fury.io/js/clawdpay-mcp.svg)](https://www.npmjs.com/package/clawdpay-mcp)

## Quick Start

```bash
npx clawdpay-mcp
```

Or install globally:
```bash
npm install -g clawdpay-mcp
```

## Manual Setup

```bash
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`:

```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

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 issues