Skip to main content
Your login determines which processes and company records your agent can access. CLI and MCP have separate sessions, so check both when switching between them. With the CLI, ultrametric auth status --json shows the locally saved session. With MCP, call status to read the account, environment, and selected organization from the service.

​
Find the right organization

Check selectedOrganizationId in the MCP status result, or organizationId in CLI login status. If the organization is missing or incorrect, complete sign-in for the intended workspace before continuing with company records. A request’s organizationId checks the selected scope. It cannot grant membership or switch the account’s organization.

​
Process availability

The process catalog lists the guides available to your account. If a process is missing, ask the agent to call MCP status with its processId. The result includes releaseAccess and available. Use IDs returned by list_processes or ultrametric process list. A process available to one account may not be available to another.

​
Context permissions

Hosted context requires active organization membership and the appropriate permissions: If a context operation is denied, check the selected organization and ask your workspace administrator to review your access. Changing a role affects access through the permissions assigned to it.

​
Token errors

Use the sign-in flow for the selected connection and environment. Tokens for another application or environment cannot be substituted. The production MCP connection uses https://auth.ultrametric.ai for OAuth. On AUTH_REQUIRED or HTTP 401, sign in again and retry the read. See CLI sign-in or MCP connection.