Skip to main content

​
Deployment

​
Server Management

Once your MCP server is deployed on Cogni+, you can easily manage its availability and status through both the web interface and CLI. This gives you full control over when your server is accessible to users.

​
Server Status Overview

Your server can be in one of several states:
  • 🟢 Active: Server is running and available to users in the marketplace
  • 🔴 Disabled: Server is temporarily unavailable but can be re-enabled anytime
  • 🟡 Pending Review: Server is under review by the Cogni+ team (new servers only)
  • ⚫ Deprecated: Server is no longer supported (permanent state)

​
Disabling Your Server

Sometimes you may need to temporarily take your server offline while keeping it deployed. This is useful for:
  • Maintenance: Performing updates or fixes without deleting the server
  • Testing: Temporarily stopping access while you test changes
  • Resource Management: Reducing costs during periods of non-use
  • Emergency Response: Quickly stopping a problematic server

​
Using the Web Interface

  1. Navigate to Your Server: Go to your Developer Dashboard and select your server
  2. Find the Disable Button: In your server’s main page, you’ll see a “Disable Server” button in the status section
  3. Confirm the Action: Click the button and confirm when prompted
  4. Verification: Your server status will change to “Disabled” and it will no longer appear in the marketplace
What happens when you disable a server:
  • The server becomes unavailable in the marketplace
  • Existing connections may be terminated (depending on configuration)
  • You stop being charged for active usage
  • All your server data and configuration remain intact

​
Using the CLI

# Disable your server
cogni server disable my-server-name

# Check server status
cogni server status my-server-name

​
Re-enabling Your Server

Getting your server back online is just as easy:

​
Using the Web Interface

  1. Go to Your Server Page: Navigate to your disabled server in the Developer Dashboard
  2. Click “Enable Server”: You’ll see an “Enable Server” button where the disable button was
  3. Instant Activation: Your server will be immediately available in the marketplace again

​
Using the CLI

# Re-enable your server
cogni server enable my-server-name

# Verify it's active
cogni server status my-server-name

​
Advanced Server Control

​
Deployment-Level Management

If you have multiple deployments (production, staging, etc.), you can manage each one independently: 
# Disable a specific deployment
cogni server disable my-server-name --deployment staging

# Enable a specific deployment  
cogni server enable my-server-name --deployment production

​
Bulk Management

For users with multiple servers, you can manage several at once: 
# Disable multiple servers
cogni server disable server1 server2 server3

# Enable all your disabled servers
cogni server enable --all-disabled

​
Understanding the Impact

​
For Server Users

  • Marketplace Visibility: Disabled servers don’t appear in search results or server lists
  • Existing Connections: Users currently connected to your server may experience disconnection
  • Bookmarks: Users who bookmarked your server will see it as “temporarily unavailable”

​
For Server Owners

  • Billing: You typically stop incurring usage-based charges when disabled
  • Data Retention: All server data, logs, and configuration remain intact
  • Metrics: Usage analytics pause while the server is disabled

​
Container and Resource Management

Important: When you disable a server, the underlying container instances are also stopped to conserve resources and minimize costs. This means:
  • Resource Conservation: CPU, memory, and storage resources are released
  • Cost Optimization: You’re not charged for idle server resources
  • Instant Restart: Re-enabling the server starts fresh container instances
  • State Considerations: Any in-memory state will be lost, but persistent data remains
For servers that maintain critical state, ensure you have proper data persistence configured before disabling.

​
Best Practices

​
Before Disabling

  • Notify Users: If your server has regular users, consider giving advance notice
  • Check Dependencies: Ensure other services aren’t depending on your server
  • Save State: Export any important temporary data that might be lost

​
Monitoring and Alerts

  • Set Up Notifications: Configure alerts for when your server goes offline unexpectedly
  • Regular Checks: Periodically verify your server status if it’s critical for your workflow
  • Usage Analytics: Review your server’s usage patterns to optimize enable/disable timing

​
Security Considerations

  • Quick Response: Use disable as a first response to security issues
  • Access Control: Ensure only authorized team members can disable production servers
  • Audit Trail: All enable/disable actions are logged for security auditing

​
Troubleshooting

​
Server Won’t Disable

If you’re unable to disable your server:
  • Check that you have the necessary permissions (owner or admin role)
  • Ensure the server isn’t in “Pending Review” status
  • Try refreshing the page and attempting again
  • Contact support if the issue persists

​
Server Won’t Re-enable

If your server won’t start after re-enabling:
  • Check the server logs for error messages
  • Verify your server configuration hasn’t changed
  • Ensure you have sufficient resource quotas available
  • Review any dependency services that might be required

​
Need Help?

For additional support with server management: