Connect
Create an API token
In the Zeabur dashboard, create a personal access token under your account’s API token settings, and copy it.Connect in Nuphos
In Connectors → Connect → Zeabur, enter:
On binding, Nuphos uses the token to discover the user and team identities it
grants, and stores the token encrypted.
In the Nuphos app
Your Zeabur servers appear in Compute & access alongside the rest of your fleet — with status and details, an SSH terminal straight into a server, and port forwarding when you need to reach something private.What the agent can do for you
The agent can list your Zeabur projects and the servers across them, and use the same SSH access to investigate. Ask it things like:- “What’s deployed across my Zeabur projects?” — it enumerates projects and servers and summarizes.
- “Check disk usage on the Zeabur server running the docs site” — it opens a shell and reports back.
Permissions & authorization
Two boundaries govern what happens through this connector:- Hard boundary — who can use it. Only team Administrators can bind or remove the token, and they can restrict it to specific members with a member allow-list. Within a session the agent only holds credentials you explicitly selected, re-checked on every request.
- Soft boundary — what the agent may do with it. Reads run freely, but changes go through plan approvals, and Auto-authorization governs each command the agent runs on a server — read-only ones auto-run, destructive ones pause for a human.
Good to know
- The token grants whatever user and team identities it was created under — Nuphos discovers these at bind time, so what you see in Nuphos mirrors what that Zeabur account can see.