Verda Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERDA_MCP_CONFIG | No | Path to the configuration file (e.g., config.yaml) containing Verda API credentials (client_id, client_secret) and default settings. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_instancesA | List all your Verda Cloud instances with their status. Returns: A formatted list of all instances with ID, hostname, status, type, and IP. |
| check_instance_statusB | Check the status of a specific instance. Args: instance_id: The ID of the instance to check. Returns: Instance status details including SSH connection info if running. |
| check_spot_availabilityA | Check if spot GPU instances are available. Uses the official Verda SDK is_available() method to check across all locations. Args: gpu_type: GPU type to check (default from config, e.g., "B300", "B200"). gpu_count: Number of GPUs (default from config, e.g., 1, 2, 4, 8). Returns: Availability status with location if available. |
| monitor_spot_availabilityA | Monitor for spot GPU availability and optionally auto-deploy when available. Polls using the official Verda SDK is_available() method until a spot becomes available. Args: gpu_type: GPU type to monitor (default from config). gpu_count: Number of GPUs (default from config). check_interval: Seconds between checks (default: 30). max_checks: Maximum number of checks before giving up (default: 60 = 30 min). auto_deploy: If True, automatically deploy when available (default: False). volume_id: Volume to attach if auto-deploying (default from config). script_id: Startup script if auto-deploying (default from config). Returns: Status updates and deployment info if auto_deploy is enabled. |
| deploy_spot_instanceA | Deploy a new spot GPU instance. Args: gpu_type: GPU type (default from config, e.g., "B300"). gpu_count: Number of GPUs (default from config, e.g., 1, 2, 4, 8). volume_id: Block volume ID to attach (default from config). script_id: Startup script ID (default from config). hostname: Instance hostname (auto-generated if not provided). image: OS image (default from config). wait_for_ready: If True, wait for instance to be ready (default: True). Returns: Instance details and SSH connection info when ready. |
| delete_instanceB | Delete an instance. Args: instance_id: The ID of the instance to delete. confirm: Must be True to actually delete (safety check). Returns: Confirmation of deletion. |
| shutdown_instanceB | Shutdown a running instance (can be restarted later). Args: instance_id: The ID of the instance to shutdown. Returns: Confirmation of shutdown. |
| start_instanceB | Start a stopped instance. Args: instance_id: The ID of the instance to start. Returns: Confirmation that start was initiated. |
| list_volumesB | List your block storage volumes. Returns: A list of volumes with ID, name, size, and attachment status. |
| list_scriptsB | List your startup scripts. Returns: A list of scripts with ID and name. |
| list_ssh_keysB | List your SSH keys. Returns: A list of SSH keys with ID and name. |
| list_imagesB | List available OS images. Returns: A list of available OS images. |
| attach_volumeA | Attach a volume to an instance. Note: The instance must be shut down first. Args: volume_id: The ID of the volume to attach. instance_id: The ID of the instance to attach to. Returns: Confirmation of attachment. |
| detach_volumeA | Detach a volume from its current instance. Note: The instance must be shut down first. Args: volume_id: The ID of the volume to detach. Returns: Confirmation of detachment. |
| create_volumeA | Create a new block storage volume. Args: name: Name for the volume (e.g., "my-data-volume"). size: Volume size in GB (default: 150GB from config). volume_type: Volume type (default: "NVMe"). Returns: Created volume details with ID. |
| get_instance_startup_scriptB | Get the startup script attached to a specific Verda Cloud instance. Args: instance_id: The ID of the instance. Returns: The script name, ID, and content, or a message if no script is attached. |
| create_startup_scriptB | Create a new startup script. Args: name: Name for the script. content: Bash script content. Returns: Created script ID. |
| create_and_set_default_scriptA | Create a new startup script and set it as the default for new instances. This creates a new script and updates config.yaml to use it as the default script_id for future instance deployments. Args: name: Name for the new script. content: Bash script content. Returns: Confirmation with script ID and updated config status. |
| set_default_scriptA | Set an existing script as the default for new Verda Cloud instances. Args: script_id: The ID of an existing script to set as default. Returns: Confirmation of the updated default. |
| show_configA | Show the current MCP server configuration (without secrets). Returns: Current configuration settings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sniper35/verda-cloud-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server