Skip to main content
Glama
liaoshengrong

Pinme Deploy MCP Server

by liaoshengrong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Pinme Deploy MCP Server

No user-submitted related servers found.

    Related Servers

    • EdgeOne Pages MCP

      BACH-AI-Tools
      A
      license
      B
      quality
      D
      maintenance
      Enables deployment of HTML content, folders, and full-stack projects to EdgeOne Pages to generate publicly accessible URLs. It utilizes EdgeOne Pages Functions and KV storage for high-performance edge delivery of web applications.
      2
      2 npm
      MIT

    • Demox MCP Server

      demox-site
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to deploy static websites to the Demox platform with automatic directory packaging and cloud storage integration. It includes tools for managing deployments, such as listing, viewing, and deleting websites.
      7
      35 npm
      MIT
    • Nippy by nippyhost

      Nippyofficial

      nippyhost
      A
      license
      Not graded
      quality
      B
      maintenance
      Publish websites from Claude, the terminal, or CI — drop a folder, get a link that doesn't expire. Wraps the nippy.host publish pipeline: create sites, update in place, read files, passwords, SEO settings, and visitor analytics.
      MIT

    • shippage

      Kaka-123-D
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables publishing HTML, markdown, text, ZIP files, and static folders to Shippage, with tools for asset uploads, page listing, updating, and deleting.
      3 npm
      MIT

    • Hostsmith MCP Server

      hostsmith
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to deploy static files and get live HTTPS URLs instantly, with support for custom domains and data residency.
      9
      54 npm
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: check_pinme_status monitors deployment status, deploy_to_pinme handles uploading content, and list_deployments retrieves deployment history. There is no overlap in functionality, making tool selection straightforward for an agent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (check_pinme_status, deploy_to_pinme, list_deployments), using snake_case throughout. This predictability enhances usability and reduces cognitive load for agents.

    Tool Count4/5

    With 3 tools, the server is well-scoped for deployment management, covering core operations like checking, uploading, and listing. It is slightly lean but reasonable, as additional tools (e.g., for deletion or updates) might be unnecessary for a simple deployment service.

    Completeness4/5

    The toolset covers essential deployment workflows: uploading, status checking, and listing. A minor gap exists in lacking a delete or update tool, but agents can work around this by re-deploying or managing deployments externally. The surface is largely complete for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources