> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Zeabur

> Connect Zeabur to see your projects and servers.

Nuphos authenticates to Zeabur with a **personal access token**, so the agent can
see your projects and servers.

## 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:

| Field         | Notes                             |
| ------------- | --------------------------------- |
| **API Token** | Your Zeabur personal access token |

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](/infrastructure/compute)
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](/security/access-control). 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](/security/approvals), and
  [Auto-authorization](/security/auto-mode) governs each command the agent runs
  on a server — read-only ones auto-run, destructive ones pause for a human.

The token carries the access of the Zeabur account that created it, so create it
from an account whose reach matches what you want the agent to have.

## 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.