Connect
Sign in from the CLI, authorize the SDK from your code, or connect an agent through MCP; every entry point reaches the same account and operations.
Connecting establishes account access before Run your first task. Choose the entry point that matches where the request comes from. The interfaces share authority requirements, but their installation, custody and execution capabilities differ. Installed clients verify delivered result bytes; hosted interfaces return delivery metadata, and the authorized recipient integration verifies the result on its delivery path. Connecting grants no authority: each required owner still approves what runs and what leaves.
Before you connect
Complete assisted setup through Request access. Agree:
- The execution route available to your account and which participant hosts and recipients it needs. Connecting alone does not establish execution readiness.
- How to obtain and verify the client bundle, install it on its supported Linux x86_64 host, and configure the CLI endpoints and account binding.
- Enrollment of each required owner host, its key custody, Space participation and approval workflow. Local MCP requires that enrolled CLI host.
- The recipient’s registration, delivery access and independent verification references.
- For local function authoring, Docker and the exact preparation image pinned by the client bundle. The CLI uses a locally present image; Standard does not distribute it through these docs. Agree its supply during setup.
The Node.js SDK invokes the installed CLI; importing the SDK does not install or enroll that CLI. The SDK and local MCP server are supplied with the client bundle. These pages do not provide a public package-install command or a self-service enrollment recipe.
Connection and execution availability
Hosted MCP can authenticate, discover tools and originate configured hosted requests. That does not make it equivalent to an installed owner’s execution path. After admission approval, if Control has not reported progress, hosted status returns hosted_continuation_unavailable: the continuation transport is not available on that path. Further polling does not start execution. Confirm the supported route during assisted setup.
Connected-source CLI requests currently require hosted custody; an installed owner’s local-file setup cannot simply be changed to --source. See Connected-source route.
CLI
Use the CLI to deploy a function with its profile, run operations, receive verified results and inspect evidence from a terminal or a script.
standard loginSign-in opens your browser. Sign in to your Standard account, review the CLI that is requesting access and approve it. The CLI keeps its credentials in your operating system's credential store, and standard status reports local credential storage, expiry and refresh uncertainty. It does not identify the signed-in account or establish that the provider still accepts the credential.