brewpage-mcp
Related Servers
Alternatives to brewpage-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP 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.10 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the OffByOne website factory, enabling agents to generate, validate, and manage full-stack web projects through safe, deterministic tools.MIT
- AlicenseAqualityAmaintenanceAn MCP server that lets AI publish markdown documents to a clean, themed web UI. One tool call creates a shareable doc.104MIT
- AlicenseAqualityAmaintenanceDeploy static websites, landing pages, and prototypes instantly. Free, no account needed.4151,411 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 20 tools
Most tools target distinct resource/action pairs, and the publish/update/get/set prefixes clarify intent. Mild overlap exists between publish_html and single-page publish_site, and between get_page and format-specific get_json/get_kv, which could cause occasional misselection.
All tool names use snake_case with a verb_noun pattern: get_limits, publish_html, update_json, delete_resource, search_gallery, mint_token, etc. The convention is predictable and consistently applied across the set.
The server covers multiple resource types, so many tools are justified, but 20 tools is on the heavy side. Granular publish/update/get operations for HTML, JSON, KV, sites, files, tokens, gallery, stats, and limits make the surface feel large and partly consolidatable.
Core lifecycle operations are present for HTML pages, JSON documents, KV stores, sites, visibility, tokens, limits, and stats. Minor gaps remain, such as explicit listing/management of owned resources and token revocation/listing, but most publishing workflows are covered.