"Cloud OS Login" is not a product named in the sources, and none of the candidates is a Google Cloud OS Login API as such. The closest match is Google Cloud Admin 6, whose page is generic Google Cloud marketing, but its Admin SDK directory actions manage Chrome OS devices rather than OS Login SSH access. Cloud OS Login is not covered by any listed source, so the closest candidates are shown for reference.
A question back: Do you mean Google Cloud OS Login, the service that manages SSH access to Compute Engine VMs through IAM? The sources here do not cover it, so I can only offer the nearest identity and login tools.
- 1
Google Cloud Admingoogle.comverified and signed
Its Admin SDK directory actions list and retrieve Chrome OS device properties for an account 16, which is device administration rather than Cloud OS Login.
official:API · Admin SDK APIskill · google-analytics-admin-api-basics
for agents: directory.chromeosdevices.list · directory.chromeosdevices.get · directory.mobiledevices.list
- 2
AWS MCP Server (yaw)yaw.shfound in code, not yet checked
An MCP server for calling AWS APIs, including SSO device-code login through aws_login_start and aws_login_complete 7, which is the closest login-related analogue on another cloud.
for agents: aws_login_start · aws_login_complete · aws_resource_create
- 3
WorkOSworkos.comverified and signed
Developer APIs and SDKs for enterprise single sign-on and directory sync 1, an identity layer rather than a Google Cloud login service.
official:MCP server · WorkOS+5 community tools built for it
for agents: workos · workos · call_integration_api
Sources
- 1WorkOS — Your app, Enterprise Ready.workos.com · read 2026-10-29
- 6AI and Cloud Computing Services | Google Cloudcloud.google.com · read 2026-10-29
- 7AWS MCP Server - yawyaw.sh · read 2026-10-29
- 16Admin SDK API: declares "directory.chromeosdevices.list" (the record we read and signed)unfragile.ai · read 2026-10-24
For agents: the 10 actions behind this answer
workos · workos verified and signed
Start new AuthKit setups with `npx workos@latest install`, which needs no WorkOS account. Use when the user asks for a WorkOS docs URL, term, or dashboard field (Sign-in endpoint, initiate_login_uri, Redirect URI, `WORKOS_*` env vars), or is implementing, debugging, or migrating WorkOS — AuthKit, SS
custom_api_call · GitHub (Activepieces) verified and signed
Custom API Call — Make a custom API call to a specific endpoint
cws-create-basic-auth-credential · Cloudflare API verified and signed
Create a basic-auth credential
clerk-backend-api · clerk-backend-api verified and signed
Clerk Backend REST API explorer and executor. Browse tags, inspect endpoint schemas, and execute authenticated requests. Use when listing users, managing organizations, or calling any Clerk API endpoint.
authentication · @descope/core-js-sdk verified and signed
directory.chromeosdevices.list · Admin SDK API verified and signed
Retrieves a paginated list of Chrome OS devices within an account.
aws_login_start · @yawlabs/aws-mcp found in code, not yet checked
Start an AWS SSO login via the device-code flow (no browser spawned from this process). Returns a verification URL and short code -- surface these to the user so they can open the URL in their own browser and paste the code. After they auth, call aws_login_complete with the returned sessionId to con
auth0 · auth0 verified and signed
Use when adding, fixing, or improving how an app authenticates users or protects an API, or when using or configuring any Auth0 feature — signing users in and out, sessions and tokens, guarding routes and endpoints, MFA, passwordless passkey login (WebAuthn), SSO, Organizations, RBAC, custom domains
cloud · @google-cloud/apikeys verified and signed
connect_agent · agent-auth found in code, not yet checked
Connect to a provider and get an agent_id. Call ONCE, then use execute_capability for everything. Typical flow: search → ask user to choose mode (if provider supports both) → connect_agent with mode → execute_capability. NEVER re-call connect_agent for the same provider unless execute_capability ret
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.