strazactl connect

Connect your own account or token to an MCP server; no server lists your connections

On this page

Synopsis

Connect your own account or token to a server that gives each caller their own credential.

On a server that uses sign-in, connect prints the address of your credentials page and waits. You sign in to Straza there and press the server’s Sign in button, so the sign-in is stored only for the person who is signed in. On a server that takes a token, connect asks for the token at a hidden prompt, or reads it from stdin when stdin is not a terminal, and never takes it as an argument. The server tests the token once and keeps only a sealed copy. The answer shows its fingerprint. With no server named, the command lists your connections.

Administrators and scripts use this command. A person connects with straza connect, or on the Credentials tab of the self-service page at /self-service/credentials. strazactl disconnect takes a connection away.

--user names an agent you sponsor, or any user when you are an administrator. --expires records the date the token stops working, as the provider shows it. --allow-agents, on its own, lets the agents you sponsor run on your connection where the server permits it. --allow-agents=false takes that back.

connect acts as a person with your strazactl login, so it refuses to run while STRAZA_API_TOKEN is set.

strazactl connect [server] [flags]

Options

      --allow-agents     let the agents you sponsor run on this connection (on its own, changes only that)
      --expires string   the date the token stops working, as YYYY-MM-DD
      --user string      act for this user: an agent you sponsor, or anyone when you are an administrator

Options inherited from parent commands

      --server string   strazad base URL (overrides $STRAZA_SERVER and the server you logged into)

See also

• strazactl: Straza admin CLI