How do I install Allowance MCP?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Allowance MCP need an API key?

No required environment variable is listed on this record.

What transport does Allowance MCP use?

Allowance MCP is reached over HTTP.

When was Allowance MCP last checked?

Last checked 2026-11-08. Secure agent purchasing with human-approved virtual cards, receipts, and audit trails.

Allowance MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.useallowance.com

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http com.useallowance-allowance-mcp https://mcp.useallowance.com

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "com.useallowance-allowance-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.useallowance.com"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.1.2
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Allowance MCP

Allowance is a payment security layer for AI agents. It lets humans approve scoped purchases on their phone while agents complete checkout with limited-use payment credentials instead of the human's real card.

Allowance MCP exposes that flow to MCP clients: agents can request approval for a specific purchase, receive a scoped virtual card after approval, complete checkout, and report receipts and final charged amounts back into an audit trail.

This repository is the public listing and configuration home for the hosted Allowance MCP server. The implementation repository is private.

Hosted Server

Server URL: https://mcp.useallowance.com
Transport: streamable-http
Official registry name: com.useallowance/allowance-mcp
Official registry URL: https://registry.modelcontextprotocol.io/v0.1/servers/com.useallowance%2Fallowance-mcp/versions/latest
Company site: https://useallowance.com
Discovery metadata: https://useallowance.com/.well-known/mcp.json
Product docs: https://useallowance.com/mcp

Authentication

Allowance MCP uses OAuth. Connect your MCP client to https://mcp.useallowance.com and complete the Allowance OAuth flow when prompted.

After OAuth completes, MCP clients send the issued bearer token on tool calls. Users should not create or paste standalone API keys for normal MCP use. Do not commit tokens, card credentials, or checkout PII.

Core Flow

The agent creates an allowance request for a specific purchase.
The human approves, denies, or lets the request expire on their phone.
If approved, the agent completes checkout with scoped payment credentials or waits for Allowance remote fulfillment.
The agent reports success or failure, including receipt and charged amount details when available.

Human phone approval is the spending authorization. After approval, agents should not ask for another final confirmation unless the realized total exceeds the approved cap, checkout requires unavailable information, or the item materially differs from the approved request.

What Allowance Controls

Spend scope: merchant, amount cap, purchase reason, and expiration.
Payment exposure: agents get limited payment credentials instead of the human's real card.
Checkout data: approved contact, shipping, and billing fields are available only when needed for checkout.
Auditability: requests, approvals, card issuance, purchase attempts, receipts, and failures are recorded.
Revocation: humans can pause or revoke allowances instead of leaving broad payment access with an agent.

Tools

send_allowance_request
poll_allowance_request
wait_for_allowance_request
get_allowance_request
list_allowance_requests
cancel_allowance_request
get_contact_details
get_allowance_shipping_address
get_allowance_billing_address
issue_allowance_card
complete_purchase_auth
report_purchase_success
report_purchase_failure
list_allowance_purchase_attempts
get_allowance
wait_for_remote_fulfillment
reply_to_remote_fulfillment_message
list_allowances
pause_allowance
revoke_allowance
list_supported_merchants
check_merchant

Security Model

Allowance is designed so agents spend with scoped authorization instead of receiving the human's real card. Approvals, limits, receipts, and audit trails are enforced by Allowance.

If you find a security issue, email [email protected].

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Allowance MCP?

Does Allowance MCP need an API key?

What transport does Allowance MCP use?

When was Allowance MCP last checked?

Documentation

Allowance MCP

Hosted Server

Authentication

Core Flow

What Allowance Controls

Tools

Security Model