MCP Servers/Pink Agentic AI Payments

Pink Agentic AI Payments

Official

MCP server that lets Claude, ChatGPT, Cursor and other AI agents request payments to vendors and invoices, checked against spending rules (budgets, caps, payee allow-lists, human approval). Sandbox preview with test money.

View Source

Pink Agentic AI Payments, by PinkWallet, puts spending rules between an AI agent and a payment. When an agent in Claude, ChatGPT, Cursor, VS Code or Windsurf is asked to pay a vendor invoice or top up API credits, it calls Pink instead of holding a card or key. Pink checks the request against the company's rules, such as per-agent budgets, single-payment caps, payee allow-lists and human approval above a threshold, before any payment credential is issued.

Every request gets one of three answers: allowed (with a single-use credential), pending_human (a person is asked first) or blocked (with the reason). The agent gets seven payment tools, including policy checks, payment requests and receipt reporting for reconciliation.

The npm package pink-agentic-payments-mcp is a local stdio bridge to Pink's remote Streamable HTTP MCP server, and clients that support remote MCP can connect to the URL directly. The service is currently a sandbox preview using test money only, and a sandbox key needs no signup.

What You Can Do

Let an AI agent pay approved vendor invoices while blocking anything over a set budget.

Require human approval for payments to new payees or above a threshold.

Give each agent its own monthly budget instead of a shared card.

Test agent payment flows safely in a sandbox with test money.

Reconcile agent-made payments by filing receipts back to Pink.

Setup Guide

Create a free sandbox key: npx -y pink-agentic-payments-mcp --create-sandbox

Add the server to your MCP client with command npx, args ["-y", "pink-agentic-payments-mcp"] and env PINK_AGENT_API_KEY set to your sandbox agent key

Or connect clients that support remote MCP directly to https://agentic-sandbox.pinkwallet.com/mcp

Restart your MCP client to load the server

Ask the agent to check or request a test payment to see allowed, pending_human and blocked decisions

How to Connect in Antigravity

To connect to a custom MCP server in Antigravity:

Open the MCP store via the "..." dropdown at the top of the editor's agent panel.

Click on "Manage MCP Servers"

Click on "View raw config"

Modify the mcp_config.json with your custom MCP server configuration.

Here is an example configuration compatible with MCP-enabled editors like Antigravity, Windsurf, Claude Desktop, and Cursor:

{
  "mcpServers": {
    "supabase-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase@latest",
        "--access-token",
        "add-token-here"
      ],
      "env": {}
    },
    "github-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "GITHUB_PERSONAL_ACCESS_TOKEN",
        "ghcr.io/github/github-mcp-server"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "add-your-token-here"
      }
    }
  }
}

This configuration defines two servers: one running via npx (Supabase) and another via docker (GitHub). Make sure to replace the placeholder tokens with your actual API keys.

For a detailed step-by-step walkthrough, check out our MCP Tutorial or explore more in our Top 10 Essential MCP Servers guide.