What are Workspaces?
Workspaces are isolated environments within the NimbleTools MCP Platform. Each workspace provides a secure, multi-tenant space where you can deploy and manage MCP servers with complete isolation from other workspaces.Key Benefits
Complete Isolation
Each workspace has isolated servers, secrets, tokens, and resources
Secure by Default
Workspace-scoped access tokens and encrypted credential storage
Easy Organization
Organize projects, environments, or teams with separate workspaces
Independent Scaling
Each workspace scales independently with its own resource limits
Workspace Architecture
Multi-Tenant Security
Each workspace operates in complete isolation:Resource Isolation
Resource Type | Isolation Level | Description |
---|---|---|
MCP Servers | Complete | Each workspace deploys its own server instances |
Secrets | Complete | API keys and credentials are workspace-specific |
Networking | Complete | Separate endpoints and routing per workspace |
Common Workspace Patterns
Environment-Based Organization
Separate workspaces for different deployment environments:Project-Based Organization
One workspace per project or application:Team-Based Organization
Workspaces for different teams or departments:Frontend Team
Frontend Team
Data Science Team
Data Science Team
DevOps Team
DevOps Team
Workspace Lifecycle
Creation and Setup
1
Create Workspace
2
Set Active Workspace
3
Configure Secrets
4
Deploy Servers
Daily Operations
Common workspace management tasks:Task | Command | Description |
---|---|---|
Switch workspace | ntcli workspace switch prod | Change active workspace |
List workspaces | ntcli workspace list | View all workspaces and active status |
View servers | ntcli server list | See deployed servers in current workspace |
Check secrets | ntcli secrets list | View configured secrets (values hidden) |
Generate tokens | ntcli token create | Create long-lived access tokens |
Cleanup and Deletion
Access Control & Security
Workspace-Scoped Tokens
Each workspace uses isolated access tokens:Credential Isolation
Secrets and API keys are completely isolated:Best Practices
Environment Separation
Use separate workspaces for dev, staging, and production
Descriptive Naming
Use clear, descriptive names and descriptions for workspaces
Secret Management
Use workspace-specific secrets, never share credentials
Regular Cleanup
Delete unused workspaces to avoid unnecessary costs
Workspace Naming Conventions
Environment-based
Environment-based
Feature-based
Feature-based
Team-based
Team-based