Using the Portal

Sign in / create your organization

Sign in at /login, or create an account — the first thing you set up is your organization's name. If someone invited you, open their invite link instead to join their organization. You can belong to several organizations and switch between them from the account menu; projects you create belong to the organization selected there.

Create a project

From the Projects page, use New project and choose a subdomain (e.g. my-backoffice → my-backoffice.uivoid.app). This is the same project the CLI would create with npx uivoid create — the portal and the CLI both talk to the same control plane, so a project started in one is fully visible and editable in the other.

Organization settings

Settingsin the top navigation shows the selected organization's members and their roles, pending invites, and an Invite member button. Owners change roles there; members see projects read-only. What each role can do is described in Teams & roles.

Databases

Databasesin the top navigation lists the hosted PostgreSQL databases in the selected organization's projects, with each one's size against the 500 MB limit, its tables and its record count. Open a database to see each table's columns and browse its rows read-only, 25 at a time. Connection details are never shown. Databases, tables and endpoints are created with the CLI (npx uivoid db create, db table create, db expose).

Inside a project

Each project has five tabs:

• Overview — status, subdomain, and how it's currently reachable.
• Tools — every MCP tool mapped to this project. Add one manually with a name, description, upstream URL, HTTP method, scope (read/write/destructive), and which outbound key it should call your API with.
• Keys— issue and revoke credentials for both directions: inbound (agent → uivoid) and outbound (uivoid → your real API), each with a secret type (bearer, HMAC, or CORS origin) and scopes. A newly created key's value is shown exactly once — copy it before closing that dialog.
• Logs — every tool call made through this project, so you can see what an agent actually did.
• Settings — choose how MCP clients authenticate to reach this project at all: uivoid organization login, fully public (no auth), or your own OAuth provider. See Authentication for the outbound side — how uivoid then authenticates itself back to your real API.

Portal or CLI?

Both are the same control plane underneath, so pick per task: the CLI's OpenAPI discovery is the fastest way to map an entire API at once (see Setup and the CLI reference), while the portal is usually easier for one-off changes — adding a single tool, rotating a key, or checking recent activity — without leaving the browser.