Connect

Connecting is the first setup step in Run your first task. Choose the entry point that matches where the request comes from. The CLI, the SDK and MCP reach the same account, the same operations and the same automatic verification, so you do not need more than one. Connecting grants no authority: each required owner still approves what runs and what leaves.

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 login

Sign-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 shows which account it is signed in to.

SDK

Use the SDK when an application, CI/CD job or backend service submits operations from its own code. It authorizes with the same account as the CLI, and verification runs inside the SDK, in your environment, before a result reaches your code.

import { Standard } from '@standardruntime/sdk';

const standard = new Standard();

The SDK mirrors the CLI one to one: standard.deploy(), standard.run() and operation.receive() do what standard deploy, standard run and standard receive do, with the same authorization and the same checks.

MCP

Use MCP to let an existing agent discover the operations its identity may request and request them within its authority.

• Endpoint: https://standardruntime.com/api/mcp
• Transport: Streamable HTTP
• Authorization: OAuth, discovered automatically from the endpoint

Add the server to your client

In clients that add remote servers through settings, such as a custom connector or integration, enter the endpoint URL. Leave any authentication fields empty: the client discovers OAuth from the endpoint.

In clients configured with a JSON file, add an HTTP server entry:

{
  "mcpServers": {
    "standard": {
      "type": "http",
      "url": "https://standardruntime.com/api/mcp"
    }
  }
}

The exact file and key names depend on your client. Use its documentation for adding a remote Streamable HTTP server.

Authorize your account

The first time the client connects, it opens a browser window:

1. Sign in to your Standard account. Accounts require multi-factor authentication.
2. Review the client that is requesting access, then approve it.
3. Return to your client. It now lists Standard's tools.

Authorizing a client lets it act within your account's permissions. It does not grant access to another owner's inputs, and it does not authorize a payment.