DCP Documentation
DCP gives AI agents controlled access to wallets, credentials, and user data without handing them private keys or raw secrets. Agents request an action; the vault checks policy, budget, and consent before returning the result.
Start Here
Install Desktop, create a vault, add data, and connect your first agent.
Run OpenClaw, Hermes, or another VPS agent while approvals stay local.
Use DCP from Claude Desktop, Cursor, VS Code, OpenClaw, Hermes, or any MCP client.
Choose the right package for Desktop, MCP, CLI, custom clients, or relay work.
Join the DCP channel for releases, issues, and integration help.
What DCP Gives Agents
- Wallet use without custody: agents can request Solana transaction, message, and x402 signatures; private keys stay in the vault.
- Scoped data access: agents request exact scopes such as
identity.emailorcredentials.api.openai. - Budget checks: DCP tracks per-transaction and daily limits for SOL, USDC, USDT, and 1LY.
- Human approvals: sensitive actions can require approval in DCP Desktop or Telegram.
- Remote agents: VPS agents use a private HTTP MCP endpoint and encrypted relay transport back to Desktop.
Current Package Set
| Package | Use |
|---|---|
@dcprotocol/desktop | Desktop app that runs the local vault runtime. |
@dcprotocol/agent | MCP, HTTP MCP, and remote VPS service. |
@dcprotocol/vault | Vault CLI and local vault server runtime. |
@dcprotocol/core | Storage, crypto, Solana wallet, policy, and shared types. |
@dcprotocol/client | Low-level runtime client used by DCP packages and advanced integrations. |
@dcprotocol/relay | Encrypted relay for remote agents. |
@dcprotocol/relay-client | Transport-level relay client used by runtime packages. |
Retired Package Names
These docs only use the package names listed above. If an older snippet uses another package name, treat it as stale and use@dcprotocol/vault for vault CLI work or @dcprotocol/agent for MCP and remote-agent work.