Skip to main content
Workspace switcher Workspaces provide isolated environments for organizing playbooks, MCP servers (toolbox), and API tokens.

​
What are Workspaces?

Workspaces are isolated containers that include:
  • Playbooks: AI-powered workflows with natural language instructions
  • Toolbox: Installed MCP servers and their configurations
  • API Tokens: Authentication tokens unique to each workspace
  • Activity Logs: Audit trail of all workspace actions
  • AI Credits: Usage tracking and billing per workspace
Think of workspaces like separate projects or environments (dev, staging, production).

​
Creating Workspaces

1

Open Workspace Menu

Click the workspace dropdown in the sidebar (shows current workspace name)
2

Click Manage Workspaces

Click the Manage Workspaces button at the bottom of the dropdown
3

Create New Workspace

Click + Create Workspace or similar option
4

Enter Details

Fill in the workspace information:
  • Name: Display name for the workspace
  • Description (optional): Purpose of the workspace
5

Create

Click Create - the workspace will be created and appear in your list

​
Workspace Naming Rules

  • Must be lowercase
  • Can contain letters, numbers, and hyphens
  • Must start with a letter
  • 3-32 characters long
  • Must be unique across your organization
Workspace names are used in server URLs: https://mcp.nimbletools.dev/{workspace-id}/{server-id}/mcp

​
Switching Workspaces

Quickly switch between workspaces:
1

Open Workspace Dropdown

Click the current workspace name in the top-left
2

Select Workspace

Choose from your list of workspaces
3

Dashboard Updates

The entire Studio interface updates to show the selected workspace
Use keyboard shortcut Cmd/Ctrl + Shift + W to quickly open the workspace switcher

​
Workspace Settings

Access workspace settings from the Settings tab:

​
General Settings

​
Workspace Name
string
Display name for the workspace (can be changed)
​
Workspace ID
string
Immutable UUID identifier used in URLs
​
Description
string
Optional description to help identify the workspace purpose
​
Region
string
Data center region (cannot be changed after creation)

​
Access Control

Manage team member access to this workspace:
RolePermissions
OwnerFull access including deletion and billing
AdminManage servers, secrets, and team members
DeveloperDeploy servers, view logs, manage secrets
ViewerRead-only access to servers and configuration
1

Navigate to Team

Go to Settings → Team Members
2

Invite Member

Click Invite Member and enter their email
3

Set Role

Choose the appropriate role for the team member
4

Send Invitation

Click Send Invite - they’ll receive an email invitation

​
Resource Quotas

View and manage resource limits for the workspace:

Max Servers

Total number of deployable servers

Max Replicas

Combined replica count across all servers

Storage

Total storage for logs and data
Resource quotas vary by plan. Upgrade your plan to increase limits.

​
Workspace Tokens

Generate tokens for CLI and API access:

​
Token Types

  • Standard Token
  • Long-Lived Token
  • Read-Only Token
  • Expires after 30 days
  • Used for CLI authentication
  • Can be refreshed

​
Generating Tokens

1

Open Token Management

Navigate to Settings → API Tokens
2

Create New Token

Click Generate Token button
3

Configure Token

  • Select token type
  • Set expiration (if applicable)
  • Add description/label
4

Copy Token

Important: Copy the token immediately - it won’t be shown again!
Store tokens securely. Anyone with a token can access your workspace!

​
Using Tokens with CLI

# Set the token as an environment variable
export NTCLI_TOKEN=your-workspace-token

# Or use the login command
ntcli auth login --token your-workspace-token

# Verify authentication
ntcli auth status

​
Deleting Workspaces

This action cannot be undone! All servers, secrets, and configuration will be permanently deleted.
1

Open Workspace Settings

Navigate to Settings → Danger Zone
2

Click Delete Workspace

Scroll to the bottom and click Delete Workspace
3

Confirm Deletion

Type the workspace name to confirm
4

Delete

Click Permanently Delete Workspace

​
Before Deleting

Make sure to:
  • ✅ Remove all servers (or they’ll be forcibly terminated)
  • ✅ Export any logs or data you need
  • ✅ Update any integrations using this workspace
  • ✅ Notify team members with access
  • ✅ Revoke all workspace tokens

​
Workspace Best Practices

Create distinct workspaces for development, staging, and production. This prevents accidental changes to production servers.
Use clear names like company-app-prod or john-experiments to quickly identify workspace purposes.
Grant team members the minimum role necessary. Use Viewer role for stakeholders who only need visibility.
Rotate workspace tokens every 30-90 days. Revoke old tokens after rotation.
Regularly check resource quotas to ensure you have headroom for growth.

Playbooks

Create AI-powered workflows in workspaces

Toolbox

Manage MCP servers in workspaces

API Tokens

Generate tokens for programmatic access

Activity Logs

Track all workspace activity
⌘I