Skip to main content
Glama

Related Servers

Alternatives to publish-pilot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to validate a remote MCP server against Claude connector directory rules — sign-in discovery, tool metadata, and listing requirements — and walk through publishing it to npm, the official MCP Registry, a Claude Code plugin repo, and the Claude connector directory one step at a time.
      53 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables to interact with GitHub repositories directly from Claude, supporting actions like viewing repos, checking status, committing and pushing changes, and managing pull requests.
      544 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read and write GitHub repositories and persist structured memory entries—prompt, plan, and result—on Turso, with search, timeline, retrieval, and soft deletion while redacting secrets.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude to GitHub repositories for querying repos, reviewing PRs, managing issues, searching code, and automating workflows.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables Claude to access and manage GitHub repositories dynamically at runtime, including private repos, with tools for browsing files, searching code, and viewing commits, pull requests, and issues.
      11
      1
      ISC

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools target distinct phases of the publishing workflow (preflight, scaffold, checks, publish, release, verify), and the descriptions clarify boundaries. Some overlap remains between run_checks, inspect_package, and verify_install, and run_command is a broad escape hatch that could be used for many tasks.

    Naming Consistency3/5

    The set is consistently snake_case, but the naming pattern is mixed: most tools are action_noun, while others are bare verbs/nouns (preflight, login, notify, job_status) or noun_verb (git_commit). The names are readable, but not predictably uniform.

    Tool Count4/5

    19 tools is slightly heavy for a typical MCP server but justified by the broad publish-and-release lifecycle. Each tool maps to a meaningful step, though the surface could be consolidated by merging related check/verify operations.

    Completeness5/5

    The surface covers the full publishing lifecycle: setup, scaffolding, validation, versioning, repo creation, CI/release workflows, publishing, trusted publishing, tagging, verification, and a safe command runner. No major dead ends are apparent for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data