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
    23,497 npm
    69
    ISC
  • A
    license
    Not graded
    quality
    C
    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
    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
    A
    maintenance
    Enables AI agents to publish HTML pages, files, or directories as public permanent links, with optional token-based updates to keep the same URL.
    2
    63 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
  • 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
    14 npm
    MIT

TDQS

A4.1/5.0

Scored across 19 tools

Disambiguation5/5

Each tool targets a clearly distinct resource+action: site lifecycle (delete/list/get/update/pause/resume/rollback), comments (list/reply/resolve/reopen), people (list/invite/remove), and auth. The only superficially close pair, publish_files vs publish_dir, is sharply separated by the descriptions (text authored here vs a folder from disk). No two tools appear to do the same thing.

Naming Consistency5/5

Every tool follows a predictable verb_noun snake_case pattern (delete_site, list_comments, invite_people, resolve_comment, etc.). The auth pair login/login_code are verb-only but read consistently with the rest. No mixed conventions or camelCase leakage.

Tool Count4/5

19 tools is at the heavier end, but the domain genuinely spans sites, comments, people, folders, and auth, and each tool maps to a real operation. Nothing looks like filler or a redundant alias, though the set is larger than the ideal 3-15 band.

Completeness4/5

Site lifecycle is well covered (publish, read, update, pause/resume, rollback, delete) plus full comment moderation and people management. Minor gaps exist — no tool to create a folder (explicitly deferred to the dashboard) and no comment deletion — but core workflows have no dead ends.

Maintenance

ActivityActive
ResponsivenessNo issues