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:
Development
Staging
Production
ntcli workspace create dev --description "Development environment" ntcli workspace switch dev # Deploy development versions ntcli server deploy nationalparks-mcp --version latest ntcli secrets set NPS_API_KEY=dev-key-here
ntcli workspace create staging --description "Staging environment" ntcli workspace switch staging # Deploy staging versions with production-like config ntcli server deploy nationalparks-mcp --version stable ntcli secrets set NPS_API_KEY=staging-key-here
ntcli workspace create prod --description "Production environment" ntcli workspace switch prod # Deploy production with scaling ntcli server deploy nationalparks-mcp --version stable ntcli server scale nationalparks-mcp 3 ntcli secrets set NPS_API_KEY=prod-key-here
Project-Based Organization One workspace per project or application:
Web Application
Mobile API
Analytics Pipeline
ntcli workspace create web-app --description "Main web application backend" ntcli server deploy nationalparks-mcp ntcli server deploy weather-mcp ntcli secrets set WEATHER_API_KEY=key1
Team-Based Organization Workspaces for different teams or departments:
ntcli workspace create frontend-team # Deploy UI-focused MCP servers ntcli server deploy ui-components-mcp ntcli server deploy design-system-mcp
ntcli workspace create data-science # Deploy ML and analytics servers ntcli server deploy ml-models-mcp ntcli server deploy data-viz-mcp
ntcli workspace create devops # Deploy infrastructure and monitoring servers ntcli server deploy monitoring-mcp ntcli server deploy deployment-mcp
Workspace Lifecycle Creation and Setup
Create Workspace
ntcli workspace create my-project --description "Project description"
Set Active Workspace
ntcli workspace switch my-project # Or use interactive selection ntcli workspace select
Configure Secrets
ntcli secrets set API_KEY=your-key ntcli secrets set DATABASE_URL=postgresql://...
Deploy Servers
ntcli server deploy nationalparks-mcp ntcli server deploy weather-mcp
Daily Operations Common workspace management tasks:
Task Command Description Switch workspace ntcli workspace switch prodChange active workspace List workspaces ntcli workspace listView all workspaces and active status View servers ntcli server listSee deployed servers in current workspace Check secrets ntcli secrets listView configured secrets (values hidden) Generate tokens ntcli token createCreate long-lived access tokens
Cleanup and Deletion Destructive Operation : Deleting a workspace removes all servers, secrets, and data permanently.
# List workspace resources before deletion ntcli server list ntcli secrets list # Delete individual resources first (optional) ntcli server remove nationalparks-mcp ntcli secrets unset API_KEY # Delete entire workspace ntcli workspace delete my-project --force
Access Control & Security Workspace-Scoped Tokens Each workspace uses isolated access tokens:
# Generate workspace-specific token ntcli workspace switch dev ntcli token refresh # Token only works for 'dev' workspace # Switch workspace, get different token ntcli workspace switch prod ntcli token refresh # Token only works for 'prod' workspace
Credential Isolation Secrets and API keys are completely isolated:
ntcli workspace switch dev ntcli secrets set DATABASE_URL=postgresql://dev-db/myapp ntcli secrets set API_KEY=dev-api-key
ntcli workspace switch prod ntcli secrets set DATABASE_URL=postgresql://prod-db/myapp ntcli secrets set API_KEY=prod-api-key
Even with the same secret names, values are completely separate and secure.
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
my-app-dev my-app-staging my-app-prod
user-auth-feature payment-integration analytics-dashboard
frontend-team backend-team data-science
Integration with Claude Desktop Each workspace can generate its own Claude Desktop configuration:
# Switch to desired workspace ntcli workspace switch prod # Generate Claude config for this workspace's servers ntcli server claude-config nationalparks-mcp
The generated configuration includes workspace-specific endpoints and tokens, ensuring Claude Desktop only accesses the intended workspace.
