SSH Teams Integration

Maverick SSH MCP can register as an SSH Teams device and use short-lived certificates for SSH authentication.

For SSH Teams platform setup and administration, start with the SSH Teams documentation.

Why Use SSH Teams with Maverick SSH MCP

• Centralize trust and access rules.
• Avoid long-lived static private keys on automation hosts.
• Use OAuth device flow for runtime registration.
• Let ssh_connect attempt certificate-based auth first, then fall back to standard auth.

Registration Flow

1. Call sshteam_register with waitForAuthorization=false.
2. Open the returned verificationUri and enter the returned userCode.
3. Call sshteam_register_poll with serverUrl and deviceCode.
4. Confirm registration with sshteam_status.

Core SSH Teams Tools

Tool	Purpose
sshteam_register	Start device registration and optionally wait for authorization.
sshteam_register_poll	Continue polling until authorization and token issuance complete.
sshteam_status	Show registrations and token state on this runtime.
sshteam_revoke_device	Revoke a registered device from the server.

Using SSH Teams During Connection

ssh_connect includes SSH Teams options:

• sshTeamEnabled (default true)
• sshTeamServer (optional override)
• sshTeamIgnoreSslTrust (default false)
• sshTeamCertificateType (ED25519 or RSA, default ED25519)
• sshTeamTimezone (optional IANA timezone)

When enabled and a registration exists, Maverick SSH MCP attempts SSH Teams certificate auth before trying configured password or key auth.

Security Notes

• Keep ignoreSslTrust=false unless you are in a controlled development environment.
• Protect local runtime state on hosts where registration credentials are stored.
• Revoke devices you no longer use with sshteam_revoke_device.