<!--
Sitemap:
- [Paybox](/index): The non-custodial wallet for AI agents
- [Getting started](/getting-started)
- [Credentials & agents](/concepts/model): The Paybox model
- [Approvals & passkeys](/concepts/approvals)
- [Request lifecycle](/concepts/requests): From intent to result
- [MCP connector](/connect/mcp)
- [OAuth 2.1](/connect/oauth)
- [MCP tools](/reference/mcp-tools): What an agent can call
- [API & endpoints](/api-reference)
- [SDK & CLI](/sdk-cli)
-->

# MCP connector

Paybox speaks the **Model Context Protocol**. Add one URL to your agent's
connector list, sign in once, and the agent gets scoped, passkey-gated access to
your wallets, cards, and secrets.

## The URL

```txt
https://api.paybox.sh/mcp
```

It's a **streamable HTTP** MCP endpoint (protocol version `2025-06-18`).

## Steps

::::steps

### Add the URL

At `claude.ai/new#settings/customize-connectors` (Customize → Connectors), `grok.com/connectors`, or your
agent's equivalent, paste the MCP URL above as a custom connector.

### Sign in

Your agent opens Paybox in a tab. Sign in (email + passkey) and **approve a
scoped grant** on just the credentials you want this agent to use, with an
approval mode per credential.

### Stay in control

Above-threshold and sensitive operations pause for your passkey. Every operation
is an audit event. Revoke the connector from the app's **Clients** screen at any
time.

::::

## How it works

The MCP endpoint is the agent's whole interface to Paybox. Adding the URL drives
an **[OAuth 2.1 + PKCE](/connect/oauth)** flow under the hood: the client
registers dynamically, you consent to a scoped grant, and the client receives an
access token it presents as `Authorization: Bearer …` on every call.

From there the agent calls the **[MCP tools](/reference/mcp-tools)** —
`list_credentials`, `request_payment`, `claim_payment_credentials`,
`request_wallet_sign`, `request_secret`, `request_swap`, `get_portfolio`,
`verify_solana_balance`,
`get_buy_link`, the x402 tools (`discover_services`, `pay_x402`, `use_service`),
`request_account_change`, `get_request`, and `list_requests` — plus any
**[plugin tools](/reference/mcp-tools#plugin-tools)** the user has enabled,
discovered through the standard MCP `tools/list`. All the same approval, policy, and audit
rules apply, and wallet signing happens in an in-chat **[signing
window](/concepts/requests#the-signing-window)** so the key never leaves MoonX
MPC.

:::tip
New to the flow? **[Request lifecycle](/concepts/requests)** explains the
submit → approve → poll pattern every tool follows.
:::
