Rackspace Spot

io.github.rackspace-spotPublished by GitHub account rackspace-spotv0.3.2Updated Oct 24, 2026

Manage Rackspace Spot Kubernetes Cloudspaces, node pools, and VMs from your AI assistant.

The publisher's own server: Spot

VerifiedStreamable HTTPWeb executableCloud & Infrastructure

Overview

AI-generated overview

Lets an AI assistant manage Rackspace Spot Kubernetes Cloudspaces, node pools and VMs, as a remote endpoint or a local Docker process.

What you can do
  • Manage Rackspace Spot Kubernetes Cloudspaces, including creating and inspecting them.
  • Manage node pools within those Cloudspaces.
  • Manage virtual machines (VMs) in the Spot environment.
  • Work against a default organization namespace, which can be overridden per tool call.
When to use it
Useful when you already run workloads on Rackspace Spot and want an assistant to inspect or change Cloudspaces, node pools and VMs without switching to the console. Less relevant if you do not use Rackspace Spot.
Requirements
A Rackspace Spot account with OAuth authentication. The remote endpoint at mcp.spot.rackspace.com can be used directly; the local option runs the Docker image rackspacengpc/spot-mcp over stdio. The local process needs the SPOT_REFRESH_TOKEN secret and optionally SPOT_ORG for a default organization namespace.
Before you install
The server manages live cloud infrastructure, so tool calls may create, change or delete Cloudspaces, node pools and VMs, which can incur Rackspace Spot costs. The local setup requires a refresh token (SPOT_REFRESH_TOKEN) that grants access to your Spot account; keep it out of logs and shared configuration.

Installation

In SourceWeft

  1. Open Rackspace Spot in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.rackspace-spot%2Fspot-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rackspace-spot": {
      "type": "http",
      "url": "https://mcp.spot.rackspace.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.2LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Spot integrations