Spaceship Mcp
Let your coding agent manage Spaceship domains, DNS, contacts, and marketplace listings without leaving the editor.
Overview
Spaceship MCP is a MCP server for the Operate phase that manages Spaceship domains, DNS records, contacts, and marketplace listings via the Spaceship API.
What is this MCP server?
- Stdio MCP package (spaceship-mcp on npm) for local agent wiring
- Manage domains and DNS records through the Spaceship API
- Update contacts and marketplace listings from agent tool calls
- Version 0.2.3 server schema aligned with MCP registry metadata
- Server version 0.2.3
- npm package identifier spaceship-mcp with stdio transport
What problem does it solve?
Switching between your agent and the Spaceship dashboard to tweak DNS or domain settings breaks flow and invites copy-paste mistakes.
Who is it for?
Indie builders using Spaceship who want Claude or Cursor to apply DNS and domain updates during ship and operate work.
Skip if: Teams on other registrars or cloud DNS-only stacks with no Spaceship account.
What do I get? / Deliverables
Your agent can perform registrar operations through MCP tools so domain and DNS changes stay traceable in the same session as your code.
- MCP tool surface for Spaceship domain and DNS operations
- Agent-callable updates to contacts and marketplace listings
- Local stdio bridge between your editor and Spaceship API
Recommended MCP Servers
Journey fit
How it compares
Registrar MCP integration, not a DNS design skill or hosting provisioner.
Common Questions / FAQ
Who is Spaceship MCP for?
Solo and indie builders who keep domains on Spaceship and use MCP-capable agents to maintain DNS, contacts, and listings.
When should I use Spaceship MCP?
Use it during launch cutovers and ongoing operate tasks when you need agent-driven domain or record changes without leaving the IDE.
How do I add Spaceship MCP to my agent?
Install the npm stdio package spaceship-mcp at version 0.2.3, add it to your MCP server config, and authenticate with your Spaceship API credentials.