# Cloud Wallet by Ekubo

> A hosted EVM wallet for AI agents, accessed through authenticated remote MCP connections.

The website manages logins, wallet setup, connections, JSON policies, owner review,
and activity. Creating a login does not create a wallet. Add wallets afterwards;
each starts with no networks enabled. Transactions are requested by authenticated
agents, not a website send form. Unmatched calls and signatures require owner
review; explicit deny rules block requests and cannot be overridden.

Policies and agent permissions are enforced by the backend. The service signer
has full delegated root authority on enabled networks; those policies are not
onchain restrictions on a compromised service signer.

## Application and documentation

- [Cloud Wallet application](https://cloud.ekubo.org/): Sign in or create a login, then add and configure wallets.
- [Agent setup instructions](https://cloud.ekubo.org/instructions): Public connection, authorization, and tool-reference guidance for Cloud Wallet and separate producer services.
- [About, terms, and privacy](https://cloud.ekubo.org/about): Product information and current legal documents.

## Connect

- [Cloud Wallet MCP endpoint](https://cloud.ekubo.org/mcp): Use a remote MCP client with Streamable HTTP and OAuth. The owner signs in, selects account access, and consents. Clients without OAuth can use an API key created by the owner in Connections → API Keys, sent in the Authorization: Bearer header. Store credentials in the client's secret storage, never in a URL.

The MCP endpoint requires authentication; an unauthenticated request returns an
OAuth discovery challenge rather than a web page. Client support depends on the
client's remote MCP and authentication capabilities.