[tea] · Pair Rust+

About

Credentials

Upload

Pair

Rust+ Connection

What this setup does and what we store on our server

📡

What this does

Connects TEARust to your Rust game server using the official Rust+ protocol — the same API the Facepunch companion app uses. Enables live player positions, event tracking, cargo docking, and push notifications from the game.

🔑

What we store

FCM token — from the Rust+ app. Lets us receive server pairing notifications and alarms.
Player token — from Rust's local files. Authenticates with your game server.
Both are stored encrypted, scoped to your squad only, never shared.

🔒

Your control

Delete all credentials at any time from this page. No ads, no tracking, no third-party data sharing. Don't trust our server? Self-host the whole app — a Docker image is available and the source is open.

Read the Privacy Policy for the full picture of what we collect and why.

Step 1

Get credentials

Choose how you want to connect

Registers TEARust with Facepunch as a Rust+ device — the same handshake the official Rust+ mobile app makes on first install. Opens your browser, you log in with Steam and click Allow on the Rust+ permission screen. The script saves a rustplus.config.json file to your current folder, then exits immediately. No background process is left running.

See every API call the script makes — full source →

Browser

CMD

Output — rustplus.config.json saved to your PC · never leaves until you upload it in Step 2

{
  "fcm_credentials":     { … },   // push notification token (from Google/Firebase)
  "expo_push_token":     "ExponentPushToken[…]", // FCM registration
  "rustplus_auth_token": "…"      // your Rust+ account token (from Facepunch)
}

How the pairing script works

Every call the script makes — no hidden steps

Firebase installation token

Creates a virtual Firebase device entry for the Rust+ companion app. This is the same first request the official Rust+ mobile app makes when you install it. Returns a short-lived auth token used in step 3.

POST firebaseinstallations.googleapis.com
  /v1/projects/rust-companion-app/installations
→ returns: installationAuthToken

GCM device check-in

Registers a virtual Android device with Google Cloud Messaging (the underlying push system Firebase uses). Returns a temporary androidId and securityToken — these are just random IDs, not linked to any real account.

POST android.clients.google.com/checkin
→ returns: androidId, securityToken

FCM push token

Exchanges the device IDs from steps 1–2 for an FCM push token. This token is what Facepunch's servers use to deliver notifications (server pairings, alarms, smart switches) to TEARust instead of to a phone.

POST android.clients.google.com/c2dm/register3
  Authorization: AidLogin {androidId}:{securityToken}
→ returns: FCM push token

Steam login via browser

Opens a local web server on port 3000 and launches your browser to Facepunch's Steam login page. You log in on Steam's own website — the script never touches your Steam password or credentials. After you click Allow, Facepunch redirects back to localhost:3000 with a Rust+ token. The script captures that token, closes the server, and exits. No credentials leave your machine — it's the same OAuth flow your phone uses.

Opens: companion-rust.facepunch.com/login  ← Steam's own page, not ours
Callback: localhost:3000/callback?token=...  ← token sent to your local machine only
→ saves: rustplus_auth_token  ← one opaque token, no username/password

Tells Facepunch "send my game notifications to this FCM token". This is identical to what happens when you pair a phone with Rust+ — you're just using TEARust's token instead of a phone. After this step the script exits and saves a local file — nothing more.

POST companion-rust.facepunch.com/api/push/register
  { AuthToken, PushToken, DeviceId: "tearust", PushKind: 3 }

✓

Output — rustplus.config.json

Three tokens saved to a local file — that's it. Here's exactly what each one is and what it cannot do:

fcm_credentials — virtual Android device IDs generated for TEARust. Not linked to any real account. Can only receive push notifications.
expo_push_token — FCM registration ID used to route those notifications. No account access whatsoever.
rustplus_auth_token — a Rust+ notification token from Facepunch. It can only receive game alerts (server paired, alarm triggered, cargo ship). It cannot log in to Steam, cannot access your Steam account, cannot perform any in-game action, and is useless outside the Rust+ notification system.

{ fcm_credentials, expo_push_token, rustplus_auth_token }

Full source — fcm-register.src.cjs View raw ↗

Loading source…