About mcp-ap2
mcp-ap2 is an MCP server for Google's Agent-to-Agent Payment Protocol (AP2), covering agent authorization, payment execution, audit trails and verifiable credentials. The package is deprecated because no live endpoint is available, and none of its tools reach a service. It is kept in the repository for reference only.
Key features
- 01Agent registration and authorization management
- 02Payment authorization and execution
- 03Audit trail and transaction queries
- 04Verifiable credential and receipt verification
Use cases
- 01Reference for AP2 authorization and audit tool design
- 02Connecting to a working AP2 endpoint through AP2_BASE_URL
MCP support
The server defines 22 tools for agent authorization, payments, audit and credentials, but it currently cannot reach a live service.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
22Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | Yes | Human-readable agent name |
| ownerEmail | string | No | Owner email for notifications |
| spendLimit | object | Yes | Spending limit for this agent |
| spendLimit.amount | string | Yes | Maximum spend amount (e.g. '1000.00') |
| spendLimit.period | enum | Yes | Limit periodper_transaction | daily | weekly | monthly |
| spendLimit.currency | string | Yes | Currency code (e.g. 'USD') |
| description | string | No | Agent description and purpose |
| capabilities | array | Yes | Agent capabilities |
Details
From the project README@codespar/mcp-ap2
Deprecated: no live endpoint. Measured on 2026-09-27:
ap2.googleapis.comanswers every path with Google's genericError 404 (Not Found)page, andsandbox.ap2.googleapis.com(used withAP2_SANDBOX=true) fails the TLS handshake, because the certificate served there covers*.googleapis.comand not the extra label. AP2 is an open specification, not an API Google hosts. No tool in this server reaches a service. The package is deprecated on npm and stays in this repository for reference only. If you have a working endpoint, point the server at it withAP2_BASE_URL. To bring the package back, open an issue in mcp-dev-latam with the provider's documented base URL.
Alpha release — published under the
alphanpm dist-tag. Pin exact versions during0.x.x-alpha. Install withnpm install <pkg>@alpha.
MCP server for AP2 — Google's Agent-to-Agent Payment Protocol (authorization, audit, and trust for agentic payments)
What is AP2?
AP2 (Agent-to-Agent Payment Protocol) is Google's open framework for authorization, audit, and trust in agentic payments. It answers the critical questions: Who authorized this payment? What limits apply? What's the full audit trail?
The specification is published at ap2-protocol.org.
Quick Start
Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": {
"ap2": {
"command": "npx",
"args": ["-y", "@codespar/mcp-ap2"],
"env": {
"AP2_API_KEY": "your-key",
"AP2_AGENT_ID": "your-agent-id"
}
}
}
}
Claude Code
claude mcp add ap2 -- npx @codespar/mcp-ap2
Cursor / VS Code
Add to .cursor/mcp.json or .vscode/mcp.json:
{
"servers": {
"ap2": {
"command": "npx",
"args": ["-y", "@codespar/mcp-ap2"],
"env": {
"AP2_API_KEY": "your-key",
"AP2_AGENT_ID": "your-agent-id"
}
}
}
}
Tools (22)
| Tool | Purpose |
|---|---|
register_agent | Register an AI agent as a trusted payer in the AP2 network. |
get_agent | Get agent registration details, trust status, and current spend usage |
list_agents | List registered agents with optional filters |
revoke_agent | Revoke an agent's payment authorization. |
authorize_payment | Request payment authorization with scoped limits. |
get_authorization | Get authorization details including status, limits, and expiry |
list_authorizations | List payment authorizations with optional filters |
execute_payment | Execute an authorized payment. |
get_audit_trail | Get the complete audit trail for a transaction — every authorization, approval, execution, and settlement e.. |
list_audit_events | List audit events across all transactions with filters |
list_payment_methods | List payment methods offered by the AP2 partner network |
get_transaction | Get full transaction details including authorization, execution, and settlement status |
list_transactions | List transactions with optional filters |
create_intent_mandate | Create an AP2 intent mandate — a Verifiable Credential expressing the user's intent to delegate a transacti.. |
create_cart_mandate | Create an AP2 cart mandate — a signed, locked-cart commitment from a merchant binding line items, totals, a.. |
create_payment_mandate | Create an AP2 payment mandate — the final Verifiable Credential authorizing settlement against a cart mandate. |
verify_credential | Verify a Verifiable Credential (intent, cart, or payment mandate). |
create_presentation | Create a Verifiable Presentation bundling one or more credentials (e.g. |
verify_presentation | Verify a Verifiable Presentation and all embedded credentials, including holder binding and challenge nonce. |
resolve_did | Resolve a Decentralized Identifier (DID) to its DID document via the AP2 universal resolver. |
create_receipt | Create a signed receipt for a settled payment — a tamper-evident record linking transaction, mandates, and.. |
verify_receipt | Verify a receipt's signature, issuer, and chain back to the originating mandates. |
Authentication
The server sends AP2_API_KEY as an Authorization: Bearer header and AP2_AGENT_ID as an X-Agent-Id header on every request (src/index.ts:69-73).
There is no portal issuing those credentials. The developer portal this README used to link, developers.google.com/ap2, answers HTTP 404, as does the ap2-spec repository it pointed at. The published specification is at ap2-protocol.org.
Environment Variables
| Variable | Required | Description |
|---|---|---|
AP2_API_KEY | Yes | Sent as Authorization: Bearer |
AP2_AGENT_ID | Yes | Sent as the X-Agent-Id header |
AP2_SANDBOX | No | true switches BASE_URL to https://sandbox.ap2.googleapis.com/v1, which fails TLS |
Use Cases
- Authorized agent purchases — Agent requests spend authorization, gets approval with limits, then executes payment
- Multi-agent commerce — Agent A authorizes Agent B to make payments on its behalf with scoped limits
- Compliance & audit — Full audit trail of every authorization, approval, execution, and settlement
- Cross-rail payments — AP2 bridges card payments, bank transfers, wallets, and x402 micropayments
Roadmap
v0.2 (planned)
create_policy— Define reusable authorization policiesdelegate_authority— Allow agent-to-agent authorization delegationget_spend_report— Get spend analytics and reports- OAuth 2.0 authentication flow
v0.3 (planned)
- Webhook support for real-time authorization events
- Multi-currency support with automatic FX
- Integration with x402 as payment method
Want to contribute? Open a PR or request a tool.
Links
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.