In-depth architectural comparison of the Spaceship MCP and Stigmer MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Spaceship MCP
Cloud Platforms · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Stigmer
Cloud Platforms · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Spaceship MCP if you need specialized Cloud Platforms tools running via a local process. Choose Stigmer if your workspace requires Cloud Platforms integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Spaceship MCP when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SPACESHIP_API_KEY, SPACESHIP_API_SECRET.
Spaceship MCP is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Stigmer belongs to Cloud Platforms using remote streaming HTTP/SSE transport. Select Spaceship MCP when you need capabilities focused on cloud platforms and Stigmer when you require tools for cloud platforms.
Create a CAA record (Certificate Authority Authorization)
create_cname_record
Create a CNAME record (canonical name)
create_https_record
Create an HTTPS record (SVCB-compatible)
create_mx_record
Create an MX record (mail exchange)
create_ns_record
Create an NS record (nameserver delegation)
create_ptr_record
Create a PTR record (reverse DNS)
+36 more tools listed on main page
Stigmer Tools (8)
query
search by method name, library, service, error message, or what you're building. Pass `library` to scope to one SDK (boto3, aws-sdk-js).
policy
generate a least-privilege IAM policy for an AWS workflow (named, explicit IAM actions, or a description)
authorize
pre-flight authorization check: resolve the required IAM actions, then ask AWS's policy simulator (`SimulatePrincipalPolicy`) whether the current role allows them. Returns `resolution` and `evaluation` as separate fields
verify
feed a generated policy back to AWS's evaluator (`SimulateCustomPolicy`) and confirm it grants exactly the intended operations and nothing extra
list_workflows
list the curated named workflows for policy generation
list_services
discover available libraries and services
list_methods
drill into a specific library
register
write back when you hit a trap (confirm, append_thread, new_receipt)