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

# Workspaces

> Isolated tenants that own servers, tools, keys, and traces.

A workspace is mcp1's tenant boundary. Every backend server, tool, API key, and trace belongs to exactly one workspace, and nothing in a workspace is visible from any other workspace — even to the same user account.

## Membership

Signing up creates your first workspace and makes you its admin. A single account can belong to more than one workspace and switch between them from the dashboard.

## What lives in a workspace

* **Backend servers** and the tools they expose
* **API keys** used to authenticate calls to the aggregated `/mcp` endpoint
* **Request logs (traces)** for every call that passed through the gateway
* **Bridges**, if you're relaying local `stdio` or LAN `http` servers in

Deleting a backend server or revoking a key only affects the workspace it belongs to.