Connect an agent

For agents: Read userland://guide/native/index through MCP resources and follow every needed section. Call context_get before choosing a workflow. Protocol conformance is not proof that every named assistant supports native creation, protected input and continuation.

Connect

Use a client that supports remote MCP over HTTPS and the authentication flow offered by the server. Add this exact address using that client’s connection settings:

https://mcp.userland.fun/mcp

The client opens Userland’s approval page. Check the client name and return website, sign in, select the intended Account and grant the required access. A read-only connection can inspect allowed state; it cannot build, deploy, run tasks or read private app diagnostics.

Native hosting is currently limited to explicitly enabled internal Accounts. A successful connection does not itself enable hosting or establish support for every client feature. The Account context reports the capabilities actually available.

Build and continue

Use the native starter prompt. The agent should recover existing apps and source, build, inspect operations, test the important flows and repair failures. When hosted commands and browsers are advertised, this can happen without a user terminal.

A later conversation starts with current context and saved app state. It does not need the previous chat’s file history. Current revision and hash preconditions prevent a stale conversation from silently overwriting newer work.

Protected input

Generated app secrets are created automatically from typed requirements. If the app needs an external provider credential, the operation returns a protected browser action. Enter the value there, never in chat or source. The agent continues the same operation after entry; the client may need to poll if it cannot receive a completion notification.

The agent may give you an optional authenticated preview link. Opening it creates your own viewing session; it is separate from the agent’s access and does not make the preview public.

Disconnect

Disconnecting in Userland’s console revokes that Userland connection. The auth_logout tool with revoke:true does the same. Removing a connection in an assistant may only remove local configuration; it is not evidence that Userland revoked the grant.

Independently issued API keys keep their own lifetime after a connector is revoked. Revoke those keys separately when desired. Do not claim disconnect removes every credential or deletes an app.