Skip to main content
Glama
acus9345

publish-pilot-mcp

by acus9345
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to publish-pilot-mcp

No user-submitted related servers found.

    Related Servers

    • ship-it-mcp

      jjm7271985
      F
      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.
      -

    • GitHub MCP Server

      maycwu
      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

    • GitHub Context MCP Server

      Haavi97
      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

    • Slipway

      Sandeepbhuiya29
      A
      license
      A
      quality
      B
      maintenance
      Enables building and shipping real apps directly from Claude or ChatGPT by scaffolding projects, editing code, running live previews with public share URLs, storing data, sending email and push notifications, deploying to hosting, and exporting finished repos.
      22
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes and detailed descriptions that delimit scope (e.g., login vs setup_trusted_publishing vs create_github_repo; job_status vs watch_workflow). A few overlaps exist: inspect_package and scan_secrets both flag secrets, and scaffold_project and add_workflows both create CI/release workflows, but the descriptions make the intended use cases mostly separable.

    Naming Consistency4/5

    All tool names use consistent snake_case, avoiding mixed conventions. However, the pattern is not uniformly verb_noun: some are bare verbs (login, notify) or noun phrases (preflight, job_status), which are minor deviations from an otherwise readable convention.

    Tool Count3/5

    21 tools is on the heavy side for a single server, falling into the 16-25 range that tends to feel bloated. Each tool does map to a distinct step in the multi-registry publish lifecycle, but the surface could likely be consolidated (e.g., helper tools like notify/open_url, or overlapping verification tools).

    Completeness5/5

    The toolset covers an end-to-end publishing lifecycle: preflight checks, tool installation, authentication, project scaffolding, workflows, git commit, GitHub repo creation, trusted publishing setup, registry dry-run inspection, publishing, tagging/releasing, workflow watching, version bumping, installation verification, project checks, secret scanning, and generic command execution. No obvious dead ends remain for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources