Sota vs Spaceship MCP
A side-by-side look at the Sota and Spaceship MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sota for cloud platforms work as a local process; choose Spaceship MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Sota when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SOTA_API_KEY, SOTA_API_URL. - You want tools like
deploy, get-logs, set-env.
Choose Spaceship MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SPACESHIP_API_KEY, SPACESHIP_API_SECRET. - You want tools like
list_dns_records, save_dns_records, delete_dns_records.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 51/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | SOTA_API_KEYSOTA_API_URL | SPACESHIP_API_KEYSPACESHIP_API_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 13 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 13 | 48 |
| Full listing | View Sota | View Spaceship MCP |
Tools & capabilities
Sota tools 13
deployDeploy an appget-logsGet build/runtime logsset-envSet environment variableget-envList environment variablesrollbackRollback to previous deploymentget-statusGet deployment statuslist-projectsList all projectscreate-projectCreate a new projectdelete-projectDelete a project permanentlyadd-domainAdd custom domain to projectlist-domainsList custom domainsget-domainGet domain details and DNS status- +1 more on the listing page
Spaceship MCP tools 48
list_dns_recordsList all DNS records for a domain with paginationsave_dns_recordsSave (upsert) DNS records — replaces records with the same name and typedelete_dns_recordsDelete DNS records by name and typecreate_a_recordCreate an A record (IPv4 address)create_aaaa_recordCreate an AAAA record (IPv6 address)create_alias_recordCreate an ALIAS record (CNAME flattening at zone apex)create_caa_recordCreate a CAA record (Certificate Authority Authorization)create_cname_recordCreate a CNAME record (canonical name)create_https_recordCreate an HTTPS record (SVCB-compatible)create_mx_recordCreate an MX record (mail exchange)create_ns_recordCreate an NS record (nameserver delegation)create_ptr_recordCreate a PTR record (reverse DNS)- +36 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Sota
{
"mcpServers": {
"sota": {
"command": "npx",
"args": [
"-y",
"@sota-io/mcp"
],
"env": {
"SOTA_API_KEY": "YOUR_SOTA_API_KEY_HERE",
"SOTA_API_URL": "YOUR_SOTA_API_URL_HERE"
}
}
}
}
Spaceship MCP
{
"mcpServers": {
"spaceship-mcp": {
"command": "npx",
"args": [
"-y",
"spaceship-mcp"
],
"env": {
"SPACESHIP_API_KEY": "YOUR_SPACESHIP_API_KEY_HERE",
"SPACESHIP_API_SECRET": "YOUR_SPACESHIP_API_SECRET_HERE"
}
}
}
}
Frequently asked questions
Sota is categorized under Cloud Platforms and uses a local stdio subprocess. Spaceship MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Sota for cloud platforms work and Spaceship MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Sota has no declared pricing — check the project's own site. Spaceship MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add sota and spaceship-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sota has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Spaceship MCP has 56/100 (Good) with 4 views, 0 installs and 13 GitHub stars.