MCP Server Automation Stable

What it is. The spore.host MCP server exposes truffle and spawn as tools for AI assistants that support the Model Context Protocol — Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP-compatible client.

When to use it. When you'd rather describe what you need in plain language — "find the cheapest A100 in us-east-1, then give me the spawn command to launch it with a 4-hour limit" — and let the assistant do the search and manage running instances, instead of typing every command yourself. It runs locally with your AWS credentials, the same trust model as the CLIs.

The MCP server cannot launch instances — by design

The exposed tools are read + manage-existing only: search / spot prices / quotas (truffle) and list / status / stop / terminate / extend (spawn). There is no launch tool, deliberately: creating billable infrastructure from an AI assistant is a boundary we don't cross automatically. The assistant helps you find the right instance and construct the spawn launch command; you run it. See the full tool list below.

Install

brew install spore-host/tap/spore-host-mcp

Configure

Claude Code — from your project directory:

claude mcp add spore-host -- spore-host-mcp
# or, with a named AWS profile:
claude mcp add spore-host -e AWS_PROFILE=my-profile -- spore-host-mcp

Claude Desktop, Cursor, Windsurf, and other clients — add to the client's MCP config (~/.claude/claude_desktop_config.json for Claude Desktop):

{
  "mcpServers": {
    "spore-host": {
      "command": "/usr/local/bin/spore-host-mcp"
    }
  }
}

Restart the client. See the setup guide for per-client config paths (Claude Code, Claude Desktop, Cursor, Windsurf, Kiro, Codex, Zed, …).

Available tools

Truffle tools

Tool	Description
truffle_find	Natural language instance type search — "nvidia h100 8gpu", "cheap arm64 with 32gb"
truffle_spot_prices	Current Spot prices for a specific type across regions and AZs
truffle_quota_check	Whether your account has sufficient quota to launch a type

Spawn tools

Tool	Description
spawn_list	List instances, filter by state and region
spawn_status	Detailed status by instance name or ID, incl. absolute reap deadline
spawn_stop	Stop or hibernate a running instance
spawn_terminate	Permanently terminate an instance — two-phase: previews first, requires confirm=true; refuses an ambiguous name
spawn_extend	Update an instance's TTL

Example interactions

"What instances do I have running and how long until they terminate?"

"Find me the cheapest GPU instance for inference in us-east-1."

"Stop the rstudio instance — I forgot it was running."

"What's the current Spot price for p4d.24xlarge across us-east-1 and us-west-2?"

"Extend the bert-training TTL by 6 hours."

Credentials

The MCP server uses whichever AWS credentials are active in your environment — the same ones the CLI uses (AWS_PROFILE/AWS_REGION, ~/.aws/…, or instance metadata). It also honors the shared spore.host config base: SPORE_PROFILE/SPORE_REGION and the [spore] table of ~/.config/spore/config.toml. No additional setup is needed if the CLI already works.

For a full setup walkthrough, see AI Assistant (MCP).

Source

The MCP server is open source and ships as a single static binary. → spore-host-mcp on GitHub