Overview
Create a new workspace with an isolated environment for your MCP servers. Workspaces provide multi-tenant security with workspace-scoped access tokens and credential isolation.Syntax
Arguments
Workspace name (must be ≤20 characters, alphanumeric and hyphens only)
Options
Optional description for the workspace
Enable verbose output to show detailed creation process
Examples
Basic Workspace Creation
Workspace with Description
Verbose Creation
Workspace Naming Rules
Workspace names must follow these rules:Length Limit
Maximum 20 characters
Character Set
Alphanumeric characters and hyphens only
Case Sensitive
Names are case-sensitive
Unique Names
Must be unique within your account
my-project
data-science-2024
prod-env
test123
my project
(spaces not allowed)this-is-a-very-long-workspace-name
(too long)prod_env
(underscores not allowed)my-project!
(special characters not allowed)
What Happens When You Create a Workspace
1
Validation
ntcli validates the workspace name and checks for conflicts
2
API Call
Creates the workspace on the NimbleTools platform
3
Activation
Automatically sets the new workspace as your active workspace
4
Token Generation
Generates initial workspace access tokens
Workspace Features
Each workspace provides:Isolated Environment
- Separate MCP servers - Each workspace has its own server deployments
- Independent scaling - Resource limits and scaling per workspace
- Isolated networking - Workspace-specific endpoints and routing
Security & Access Control
- Workspace-scoped tokens - Access tokens limited to workspace resources
- Credential isolation - Secrets and API keys are workspace-specific
- Independent permissions - User access controlled per workspace
Resource Management
- Resource quotas - CPU, memory, and storage limits per workspace
- Cost tracking - Usage and billing tracked per workspace
- Monitoring - Logs and metrics isolated per workspace
Free Tier: Each account includes generous free tier limits. Additional workspaces and resources available with paid plans.
Post-Creation Steps
After creating a workspace, you typically want to:- Deploy Servers
- Set Secrets
- Generate Tokens
Managing Multiple Workspaces
Common patterns for workspace organization:Environment-based
Environment-based
Separate workspaces for different environments:
Project-based
Project-based
One workspace per project or application:
Team-based
Team-based
Workspaces for different teams or purposes:
Error Handling
Name already exists
Name already exists
Error: “Workspace name already exists”Solution: Choose a different name or check existing workspaces:
Invalid name format
Invalid name format
Error: “Invalid workspace name format”Solution: Follow naming rules (≤20 chars, alphanumeric + hyphens):
Authentication required
Authentication required
Error: “Authentication required”Solution: Login first:
Quota exceeded
Quota exceeded
Error: “Workspace quota exceeded”Solution: Delete unused workspaces or upgrade your plan:
Related Commands
workspace list
List all your workspaces and see which is active
workspace switch
Switch between existing workspaces
workspace delete
Delete a workspace and all its resources
server deploy
Deploy MCP servers to your new workspace
Next Steps
After creating a workspace:- Set secrets:
ntcli secrets set API_KEY=value
- Deploy servers:
ntcli server deploy nationalparks-mcp
- Generate tokens: `ntcli token refresh
- Test integration:
ntcli mcp tools server-name
Tip: The newly created workspace is automatically set as active. You can start deploying servers immediately!