Skip to main content
Glama

Related Servers

Alternatives to drop2run-mcp

  • A
    license
    B
    quality
    B
    maintenance
    Enables code agents to interact with Netlify services through the Model Context Protocol, allowing them to create, build, deploy, and manage Netlify resources using natural language prompts.
    10
    52,122 npm
    71
    ISC
  • A
    license
    Not graded
    quality
    D
    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

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables an AI agent to pack a local folder and deploy it as a live static website at a public URL, with no account required for the first publish. Also supports checking site activation, listing existing sites with their status and views, and recovering access to a site whose key was lost.
    4
    60 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Send a live, private link to a client from Claude. SnapHost publishes what your assistant builds as a shareable website with a stable URL, updates it in place, restricts viewers by email or password, rolls back bad versions, serves custom domains, and stores form and waitlist data with no backend.
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Publish pages, documents, or folders to a public link. Anonymous links last 30 days; optional account authentication enables permanent storage and updates that keep the same URL.
    2
    320 npm
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to publish static sites and build folders as live websites, push updates, provision and manage custom domains with DNS, and send transactional email. Ships as a local pip/uvx server that reads build folders directly, or as a hosted HTTP endpoint for Claude Code, Claude Desktop, and other MCP clients.
    11
    MIT

TDQS

A4.1/5.0

Scored across 20 tools

Disambiguation5/5

Each tool targets a distinct resource and action: publishing (publish_files vs publish_dir, split cleanly by text-vs-disk), auth (login vs login_code, split by browser availability), site lifecycle, people, and comments. Overlaps like pause_site/delete_site and resolve_comment/reopen_comment are explicitly differentiated in the descriptions. No two tools appear to do the same thing.

Naming Consistency5/5

Every tool follows a consistent snake_case verb_noun pattern (publish_files, list_sites, get_site, update_site, pause_site, invite_people, reply_comment, resolve_comment, reopen_comment). The only verb-only names, login/login_code, form a clear pair and don't break readability.

Tool Count4/5

20 tools is slightly on the heavy side but each maps to a real operation across four coherent areas (publishing, auth, site management, people, comments). Nothing looks like filler, though it sits at the upper edge of a comfortable set.

Completeness4/5

The surface covers the full lifecycle: publish, read, update, pause/resume, rollback, delete, plus people and comment management. Minor gaps exist (e.g. no dedicated site-creation or folder-management tool, and folder creation is only in the dashboard), but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues