Skip to main content
Glama

Related Servers

Alternatives to drop2run-mcp

  • A
    license
    B
    quality
    A
    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.
    9
    45,458 npm
    65
    ISC
  • 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

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.
    4
    2
    221 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
    15 npm
    MIT

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

login and login_code are clearly differentiated by environment (browser vs. headless), and publish_files vs publish_dir are distinguished by input type (files vs directory). However, the boundary between publishing text content and static files could be slightly clearer, as both result in a site.

Naming Consistency4/5

All tool names use snake_case and follow a verb_noun or noun_verb pattern (login_code, publish_files, delete_site, list_sites). The only minor deviation is 'login' lacking a noun, but it's intuitive and consistent overall.

Tool Count5/5

Six tools provide a well-scoped set covering authentication, publishing, deletion, and listing. Each tool earns its place without redundancy or excessive granularity.

Completeness4/5

The surface covers authentication, publishing, listing, and deletion, which are the core operations for managing sites. Minor gaps include no explicit update or rename for existing sites, and no tool to retrieve a site's metadata or content, but these are workaroundable by re-publishing or listing.

Maintenance

ActivityMaintained
ResponsivenessNo issues