Skip to main content
Glama
Sign In
spaceship-mcp

spaceship-mcp

by BartWaardenburg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to spaceship-mcp

No user-submitted related servers found.

    Related Servers

    • spaceship-mcp

      bearded-giant
      A
      license
      A
      quality
      B
      maintenance
      Enables natural-language management of Spaceship domains, DNS records, contacts, and marketplace listings through any MCP-compatible AI client. It adds TXT records without clobbering existing ones, restores records when a save fails, and can read API credentials from 1Password references.
      48
      118 npm
      MIT

    • spaceship-mcp

      heaventree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for reading and changing DNS records via the Spaceship API, with reviewable two-step confirmation and safety restrictions. It exposes only safe DNS operations, using domain allowlisting and failing closed when not configured.
      118 npm
      MIT

    • shipmail-mcp

      shipmail-to
      A
      license
      B
      quality
      A
      maintenance
      Official MCP server for Shipmail, enabling agents to manage domains, mailboxes, messages, threads, webhooks, and suppressions via natural language.
      100
      829 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially across different domains (domain management, DNS, contacts, seller hub). However, the many DNS record creation tools (e.g., create_a_record, create_cname_record) are very similar in behavior and warnings, which could cause some confusion despite clear record-type differentiation.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., check_domain_availability, set_auto_renew, create_cname_record). No mixing of conventions or vague verbs.

    Tool Count3/5

    48 tools is a high count, but the server covers multiple subdomains (domain registration, DNS management, contacts, seller hub). While each tool has a clear role, the number feels borderline heavy for a typical MCP server, partly due to many per-record-type DNS tools.

    Completeness4/5

    The server provides comprehensive coverage for domain lifecycle (register, renew, restore, transfer, contacts, privacy, nameservers) and extensive DNS record management. Minor gaps like missing batch operations or advanced DNS features (e.g., dynamic DNS) are acceptable for the scope.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources