brewpage-mcp
Related Servers
Alternatives to brewpage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.8 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the OffByOne website factory, enabling agents to generate, validate, and manage full-stack web projects through safe, deterministic tools.MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets AI publish markdown documents to a clean, themed web UI. One tool call creates a shareable doc.104MIT
- AlicenseAqualityBmaintenanceDeploy static websites, landing pages, and prototypes instantly. Free, no account needed.4151,002 npm6MIT

CustomJS MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceA remote MCP server that enables AI agents to host HTML pages, generate PDFs, capture screenshots, scrape sites, and run sandboxed code using a CustomJS API key.MIT- AlicenseAqualityDmaintenanceA general-purpose MCP server providing web search, persistent memory storage, and secure code execution capabilities. It enables AI agents to search the web, store and retrieve data, and run Python/JavaScript code in sandboxed environments.8MIT
TDQS
Scored across 32 tools
Most tools map to distinct resources (json, kv, site, domain, page data), but the publish family overlaps heavily: publish_file can produce an HTML page, which collides with publish_html, and update_html vs update_json vs republish_site require careful reading of long descriptions to choose correctly. get_page vs get_json vs get_kv is separable, but the boundary between 'file' and 'page' depends on server-side extension detection that the agent cannot predict.
Nearly all 32 tools follow snake_case verb_noun: publish_*, get_*, set_*, update_*, delete_*/remove_*. A few deviations (make_private uses an adjective, delete_resource and delete_page_data use different verbs than remove_domain) are minor and readable.
32 tools is heavy for a single publishing service, and several are near-duplicates in scope (publish_html/publish_file/publish_site, update_html/update_json). The domain-management and page-data clusters are justified, but the publish surface could be consolidated into fewer parameterized tools.
Coverage is broad: create/update/delete for HTML, JSON, KV, sites, full custom-domain lifecycle, page-data read/write/configure/delete, stats, limits and gallery search. Main gaps are no way to list or enumerate your own publications and no per-key KV deletion or KV read/list of keys beyond get_kv.