Skip to main content
Workspaces are containers for gateways and their telemetry data within Ultra Hub. Use workspaces to organize your MCP infrastructure by environment, team, or purpose.

​
What’s in a Workspace

A workspace contains:
  • Gateways — Ultra instances linked to this workspace
  • Traces — MCP operation traces synced from linked gateways
  • Audit events — Security audit events from linked gateways
  • Server statistics — Aggregate data about upstream MCP servers

​
Typical Organization

Organization
└── Team (Engineering)
    ├── Workspace: Development
    │   ├── alice-macbook (gateway)
    │   ├── bob-macbook (gateway)
    │   └── charlie-macbook (gateway)
    ├── Workspace: Staging
    │   └── staging-ci (gateway)
    └── Workspace: Production
        ├── prod-gw-1 (gateway)
        └── prod-gw-2 (gateway)

​
Common Patterns

  • By environment — Development, Staging, Production
  • By team — Frontend, Backend, Data Science
  • By project — Project Alpha, Project Beta

​
Selecting a Workspace

When you run ultra link, you select a workspace for your gateway: 
# Interactive — shows a list of your workspaces
ultra link

# Direct — link to a specific workspace
ultra link --workspace ws_xxxxxxxxxxxx

​
Workspace Data Isolation

Each workspace’s data is isolated:
  • Traces from Workspace A are not visible in Workspace B
  • Audit events are scoped to the workspace
  • Gateway health is tracked per workspace
  • Statistics and aggregations are workspace-scoped
This makes workspaces suitable for environment separation where development data shouldn’t mix with production data.

​
Managing Workspaces

Workspaces are currently managed through the Hub web interface. During onboarding, you create your first workspace. Additional workspaces can be created from the Hub dashboard.