Purpose
mcp-server-spotinst is an MCP server for the Spot.io (Spotinst) API, designed to let users manage Spot.io resources in cloud environments through the MCP protocol. It supports both AWS and Azure clouds and supports multi-account access.
Main Capabilities
- Supports Ocean clusters on AWS and Azure (Azure requires passing cloud="azure").
- Supports Stateful Nodes (AWS Managed Instances).
- Covers scheduling and health-related functionality.
- Provides write operations, but confirm=true must be passed for them to execute.
- All tools accept an optional account_id parameter, which can be used to query any account.
- Provides a remove_instances tool to remove instances through a policy-based safe interface instead of memorizing API flags. When confirm=false (the default), the tool shows a detailed execution plan for the user to review first.
- You can use list_accounts to view all accessible accounts, then pass account_id to any tool; you can also use list_all_clusters to get the cluster inventory for all accounts in one call.
Usage
Can be installed via pip, or run without installation via uvx.
Claude Code configuration: add the following content to ~/.mcp.json (the materials do not provide the specific JSON content).
Multi-account usage example: when using a personal API token to access multiple Spotinst accounts, first use list_accounts to view available accounts, then pass account_id to any tool; or use list_all_clusters to get the full inventory in one call.
This server uses the Spot.io REST API located at https://api.spotinst.io .
Suitable Scenarios
Suitable for users who need to manage Spot.io Ocean clusters, VNGs, and Elastigroups on AWS or Azure, and who care about cost, right-sizing, and logging operations, especially in scenarios involving centralized multi-account management and secure review of write operations.
Limitations
The materials do not provide specific installation command details, a complete list of environment variables, detailed parameters for each tool, free or paid information, platform limitations, and so on; related content is not yet provided.
