Gemini CLI

Gemini CLI signs in to Sallyport by itself. It keeps MCP servers in ~/.gemini/settings.json for your user and in .gemini/settings.json for one project.

Connect it

• Run the command below.
• In Gemini CLI, type /mcp auth sallyport. Your browser opens Sallyport.
• Sign in or create an account, then press “Allow” on the consent screen.

gemini mcp add --scope user --transport http sallyport https://mcp.sallyport.cloud/mcp

Pressing “Allow” creates an agent named after the client. An owner’s or admin’s agent starts with every connection of the workspace. A member’s agent starts with none, and an admin adds them under “Access”. Signing in again later takes one “Reconnect” click.

Connect with a token

On a machine where nobody signs in, Gemini CLI sends an agent token as a header.

• In the console, open Agents, press “New agent”, type a name and press “Create agent”.
• On the agent’s page, under “Tokens”, press “New token” and copy it. It is shown once.
• Run the command below with your token in place of YOUR_AGENT_TOKEN.

gemini mcp add --scope user --transport http \
  --header "Authorization: Bearer YOUR_AGENT_TOKEN" \
  sallyport https://mcp.sallyport.cloud/mcp

Without --scope user, the command writes to the project’s .gemini/settings.json, and the token would travel with the repository. The command above writes this entry:

{
  "mcpServers": {
    "sallyport": {
      "httpUrl": "https://mcp.sallyport.cloud/mcp",
      "headers": { "Authorization": "Bearer YOUR_AGENT_TOKEN" }
    }
  }
}

When a call waits for a person

Gemini CLI waits up to 10 minutes for a tool by default. Sallyport holds a waiting call for at most 4 minutes, so its answer always arrives in time.

If nobody answered yet, the answer carries approve_url and call_id. Answer the card, then tell the agent to continue: it repeats the call with that call_id, and the service is called once.