# MCP wallet setup (/docs/swivy/mcp-setup)

This self-service connection is a **testnet preview**. It can list and create wallets; it cannot sign, transfer, export keys or create delegation grants.

## Register the client [#register-the-client]

An operator registers the client with exact callback URLs, **S256 PKCE**, and these scopes:

```text
openid wallets.read wallets.create
```

Use the resource origin and App ID supplied for your environment:

```text
Resource: RESOURCE_ORIGIN/mcp
Issuer:   RESOURCE_ORIGIN/oidc/APP_ID
```

Public dynamic client registration is not available. Do not substitute the public docs/dashboard alias for the provisioned resource origin.

## Connect as the user [#connect-as-the-user]

The user signs in with an enabled email or SMS method and approves the displayed permissions. Customer login and delivery must be configured first; see [preview setup](/docs/swivy/preview-setup).

The client can then call:

```text
swivy_list_wallets {}
swivy_create_wallet { "chain": "evm" }
swivy_create_wallet { "chain": "solana" }
```

Creation requires `wallets.create` plus app policy allowing managed accounts, managed custody and the selected agent chain. It creates or reuses the signed-in subject's wallet and returns public details.

Provisioned signing connections require separately approved [delegated limits](/docs/swivy/delegated-limits). Wallet creation permission does not confer spending permission, and software custody in staging does not establish production custody readiness.
