Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirA community-built Model Context Protocol (MCP) server for the Spaceship API. Manage domains, DNS records, contacts, marketplace listings, and more — all through natural language via any MCP-compatible AI client.
Note: This is an unofficial, community-maintained project and is not affiliated with or endorsed by Spaceship.
CLI one-liners — the fastest way to get started. Pick your tool:
claude mcp add --scope user spaceship-mcp \
--env SPACESHIP_API_KEY=your-key \
--env SPACESHIP_API_SECRET=your-secret \
-- npx -y spaceship-mcp
codex mcp add spaceship-mcp \
--env SPACESHIP_API_KEY=your-key \
--env SPACESHIP_API_SECRET=your-secret \
-- npx -y spaceship-mcp
gemini mcp add spaceship-mcp -- npx -y spaceship-mcp
Set environment variables SPACESHIP_API_KEY and SPACESHIP_API_SECRET separately via ~/.gemini/settings.json.
Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) > MCP: Add Server > select Command (stdio).
Or add to .vscode/mcp.json in your project directory:
{
"servers": {
"spaceship-mcp": {
"type": "stdio",
"command": "npx",
"args": ["-y", "spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "your-key",
"SPACESHIP_API_SECRET": "your-secret"
}
}
}
}
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"spaceship-mcp": {
"command": "npx",
"args": ["-y", "spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "your-key",
"SPACESHIP_API_SECRET": "your-secret"
}
}
}
}
This MCP server works with any client that supports the Model Context Protocol, including:
Cowork runs inside Claude Desktop and uses the same connected MCP servers and permissions. Configure once in Claude Desktop, then the server is available in Cowork.
Add the following to your Claude Desktop config file:
{
"mcpServers": {
"spaceship-mcp": {
"command": "npx",
"args": ["-y", "spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "your-key",
"SPACESHIP_API_SECRET": "your-secret"
}
}
}
}
Windsurf — add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"spaceship-mcp": {
"command": "npx",
"args": ["-y", "spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "your-key",
"SPACESHIP_API_SECRET": "your-secret"
}
}
}
}
Cline — open Settings > MCP Servers > Edit, then add the same mcpServers block shown above.
Zed — add to your Zed settings (~/.zed/settings.json on macOS, ~/.config/zed/settings.json on Linux):
{
"context_servers": {
"spaceship-mcp": {
"command": "npx",
"args": ["-y", "spaceship-mcp"],
"env": {
"SPACESHIP_API_KEY": "your-key",
"SPACESHIP_API_SECRET": "your-secret"
}
}
}
}
docker run -i --rm \
-e SPACESHIP_API_KEY=your-key \
-e SPACESHIP_API_SECRET=your-secret \
ghcr.io/bartwaardenburg/spaceship-mcp
Use this as the baseline in any host:
npx["-y", "spaceship-mcp"]SPACESHIP_API_KEY, SPACESHIP_API_SECRETSPACESHIP_CACHE_TTL, SPACESHIP_MAX_RETRIES, SPACESHIP_TOOLSETS, SPACESHIP_DYNAMIC_TOOLS (see Configuration)Host key mapping:
If you prefer editing ~/.codex/config.toml directly:
[mcp_servers.spaceship-mcp]
command = "npx"
args = ["-y", "spaceship-mcp"]
env = { "SPACESHIP_API_KEY" = "your-key", "SPACESHIP_API_SECRET" = "your-secret" }
For any MCP-compatible client, use this server configuration:
npx["-y", "spaceship-mcp"]SPACESHIP_API_KEY and SPACESHIP_API_SECRETClaude currently has multiple MCP-related concepts that are easy to mix up:
claude_desktop_config.json and started on your machine (docs).Verified against vendor docs on 2026-03-05.
What is portable across hosts:
command, args, env)stdio command server)What is host/vendor-specific (not portable as-is):
servers, mcpServers, context_servers, mcp_servers)Retry-After header supportGenerate your credentials in the Spaceship API Manager.
Each scope controls access to a specific part of the Spaceship API. When creating your key, enable only the scopes you need.
The table below shows which scopes are required for each group of tools.
Full access — enable everything for unrestricted use:
domains:read domains:write domains:billing domains:transfer
contacts:read contacts:write
dnsrecords:read dnsrecords:write
sellerhub:read sellerhub:write
asyncoperations:read
DNS management only — just read/write DNS records:
dnsrecords:read dnsrecords:write
Read-only — browse domains and records without making changes:
domains:read contacts:read dnsrecords:read sellerhub:read asyncoperations:read
Each DNS record type has a dedicated tool with type-safe parameters and validation.
Resources provide passive context that clients can load without calling tools.
Clients that support resource subscriptions will receive automatic notifications when data changes (polled every 30 seconds).
Prompts provide guided workflows that clients can present as slash commands or quick actions.
These prompts support argument auto-complete for domain names and common values:
Reduce context window usage by enabling only the tool categories you need. Set the SPACESHIP_TOOLSETS environment variable to a comma-separated list:
SPACESHIP_TOOLSETS=dns,domains
When not set, all toolsets are enabled. Invalid names are ignored; if all names are invalid, all toolsets are enabled as a fallback.
For agents with constrained context windows, dynamic mode replaces all 48 tools with 3 lightweight meta-tools:
SPACESHIP_DYNAMIC_TOOLS=true
Workflow:
search_tools({ query: "dns" }) — discover relevant toolsdescribe_tools({ tools: ["create_a_record"] }) — get the full parameter schemaexecute_tool({ tool: "create_a_record", arguments: { ... } }) — executeResources, prompts, and completions remain available in dynamic mode.
register_domain, create_*, update_*, delete_*, save_*, set_*, and lifecycle operations).Once connected, you can interact with the Spaceship API using natural language:
# Install dependencies
pnpm install
# Run in development mode
pnpm dev
# Build for production
pnpm build
# Run tests
pnpm test
# Type check
pnpm typecheck
src/
index.ts # Entry point (stdio transport)
server.ts # MCP server setup, toolset filtering, feature registration
spaceship-client.ts # Spaceship API HTTP client with caching and retry
cache.ts # TTL-based in-memory response cache
schemas.ts # Shared Zod validation schemas
output-schemas.ts # Zod output schemas for all 48 tools
types.ts # TypeScript interfaces
tool-result.ts # Error formatting with recovery suggestions
resources.ts # MCP Resources (5 resources)
resource-subscriptions.ts # Polling-based resource change notifications
prompts.ts # MCP Prompts (5 guided workflows)
completions.ts # MCP Prompts with argument auto-complete (4 prompts)
dynamic-tools.ts # Dynamic tool loading meta-tools
dns-utils.ts # DNS record formatting utilities
update-checker.ts # NPM update notifications
tools/
dns-records.ts # List, save, delete DNS records
dns-record-creators.ts # 13 type-specific DNS record creation tools
domain-management.ts # Domain listing, settings, nameservers
domain-lifecycle.ts # Registration, renewal, transfer, restore
contacts-privacy.ts # Contact profiles and WHOIS privacy
personal-nameservers.ts # Vanity/glue nameserver management
sellerhub.ts # Marketplace listing and checkout tools
analysis.ts # DNS alignment analysis
MIT - see LICENSE for details.
MCP server for the Spaceship API — manage domains, DNS, contacts & marketplace listings via AI
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Spaceship roda localmente via stdio.
Última verificação: 2026-10-28. MCP server for the Spaceship API — manage domains, DNS, contacts & marketplace listings via AI