Multiple accounts

You can belong to several accounts — production and staging, or a client's account beside your own. A connection binds one account, so working across several means one connection per account, named so you and the model can always tell them apart.

One connection, one account#

An emk- key belongs to the account that minted it, and a cloud connector's authorization is granted for one account you choose in the browser. A connection does not switch accounts mid-conversation — the account is decided when you wire it up, which is what keeps every run and audit event attributed to the right place.

One MCP server entry per account#

For a client that runs the emisar-mcp bridge — Claude Code, Cursor, and the other local clients — mint a key in each account's AI agents page, then add one server entry per account. Put the account in the entry's name: the client namespaces tool calls by that name, so "check staging" has an unambiguous target and the model cannot mix accounts up.

{
  "mcpServers": {
    "emisar-prod": {
      "command": "emisar-mcp",
      "env": {
        "EMISAR_URL": "https://emisar.dev",
        "EMISAR_API_KEY": "emk-…the prod account's key…"
      }
    },
    "emisar-staging": {
      "command": "emisar-mcp",
      "env": {
        "EMISAR_URL": "https://emisar.dev",
        "EMISAR_API_KEY": "emk-…the staging account's key…"
      }
    }
  }
}

The snippet shape and each client's config location are in Connect a CLI agent — the console generates a ready snippet per client, and a client registered with claude mcp add takes a second registration under the other name.

The CLI: stored accounts#

The bridge is also a shell CLI, and it holds credentials for several accounts at once. Run emisar-mcp auth once per account — it opens the browser, you choose the account, and the credential is stored locally. Then:

emisar-mcp accounts list
CURRENT  ACCOUNT         SLUG  ENDPOINT
*        Northstar Labs  demo  https://emisar.dev
         Acme Logistics  acme  https://emisar.dev

The star marks the current account — the one commands use when you name none. Switch it, or point a single command somewhere else without switching:

emisar-mcp accounts use acme
Using Acme Logistics (acme) at https://emisar.dev

emisar-mcp --account demo recent_runs

--account is how an agent works across accounts from one shell: tell it which account each command targets, and the audit trail in each account shows exactly what ran there. When EMISAR_URL and EMISAR_API_KEY are both set, that pair wins — direct commands use it, and --account is refused until you unset both. The complete command surface is in MCP CLI & reference.

Cloud connectors: one per account#

Claude.ai and ChatGPT hold one authorization per connector, and the authorization is granted for one account you choose on the consent screen. To connect multiple accounts, add a connector for each one and name it for its account. You sign in with the same email each time. The walkthroughs are in Connect Claude.ai and Connect ChatGPT.

Every key and connector appears on that account's AI agents page under the member who created it, with its own activity, rotation, and revoke — Manage agents & keys covers the lifecycle.