AI Agent Hub
Back to skills
COROS MCP Login Gateway icon

COROS MCP Login Gateway

AI Agent Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @coros/coros according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

When COROS MCP sits behind the mcp.coros.com gateway, a client has to handle regional issuer selection, browser login callbacks, interrupted terminals, isolated CN/EU/US token state, and multi-step CLI state. Manual use can easily mix regional login state, lose the login handoff when the browser opens on another machine, or slow down tool discovery by repeatedly querying /mcp.

How It Works

The skill organizes the flow around a local helper:
- Gateway login: it reads the issuer from discovery and pins login, refresh, MCP calls, and local cache to the same region.
- Two-step login: when the browser may be on another machine or the terminal may be interrupted, login-start / login-finish preserve pending state so the completed browser login can be saved.
- Tool calls: list-tools, describe-tool, and call-tool reuse token cache and a short-TTL tool catalog cache, with forced refresh only when needed.
- Safety: tokens are not printed to stdout, error messages are sanitized, MCP requests use stateless /mcp, and no Mcp-Session-Id dependency is required.

Boundaries

It fits scenarios that need stable COROS MCP login, tool discovery, and tool invocation. If the user is not logged in, browser-based COROS login is still required; if regional behavior matters, note whether the gateway resolved to CN, EU, or US. It does not create COROS accounts, does not replace COROS business semantics, and asks only for missing required arguments instead of dumping the full schema.

Use Cases

  • Save a COROS token after a cross-machine browser login with two-step login.
  • Check the gateway issuer and local cache before choosing CN, EU, or US.
  • List COROS MCP tools, inspect the schema, then pass JSON tool arguments.
  • Reuse cached login and refresh tokens before stateless /mcp calls.

Best For

  • Engineers who want an AI agent to log in to COROS and call MCP tools.
  • Platform engineers maintaining multi-region COROS state and token isolation.
  • Automation staff who need login to persist when browser opens elsewhere.
  • Integration engineers inspecting tool schemas and requesting missing args.