All servers / Web / BrewPage MCP server
BrewPage MCP server
MCP server for BrewPage — publish and manage HTML, sites, KV, JSON and files from AI assistants, including pages that save visitor answers (forms, polls) with P
Tested by ConnectATDScore 85 out of 100. Tested 2026-11-18 on package version 2.1.2. Package: brewpage-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 15 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.0 seconds including download)
- Tools offered: 25
- Last published: 2026-11-17
- Weekly downloads (npm): 2,763
- License: MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
publish_html10 of 14 parameters describedPublish a page (`content`: HTML, Markdown, code or JSON, max 5 MiB) or a static site (`files`: HTML, CSS, JS as text; 200 files, 20 MiB in total). Returns the share link, the owner token and manageUrl (private: its holder can edit or delete). Owner tokens and management links never go into published content. A page that saves what visitors enter needs `state` and the script named in guide topic `page-data`. Page code must not hide or alter the BrewPage badge; a profile can turn the badge off for a page.
publish_file4 of 6 parameters describedPublish a file fetched from a public http(s) URL, not a local path (max 5 MiB, video 20 MiB); HTML and Markdown files become pages. Returns the share link, the owner token and manageUrl (private: its holder can edit or delete). Owner tokens and management links never go into published content.
delete_resource0 of 4 parameters describedDelete a publication for good.
get_page3 of 6 parameters describedRead stored content: a page (rendered HTML, or its code or text), a JSON document or a KV value; long content is cut and continues by `offset`.
get_stats1 of 1 parameter describedPlatform-wide counts of publications created, deleted and viewed, today and all time.
update_html5 of 9 parameters describedReplace the content of an existing page (`content`) or every file of an existing site (`files`; files absent from the upload are removed). The link stays. Page code must not hide or alter the BrewPage badge; a profile can turn the badge off for a page.
publish_json4 of 6 parameters describedPublish a JSON document (max 1 MiB). Returns the share link, the owner token and manageUrl (private: its holder can edit or delete). Owner tokens and management links never go into published content.
update_json1 of 4 parameters describedReplace an existing JSON document.
publish_kv3 of 7 parameters describedCreate a KV store with its first entry (max 1 MiB per value, 1,000 keys); the key `hosting` is reserved. Returns the share link, the owner token and manageUrl (private: its holder can edit or delete). Owner tokens and management links never go into published content.
set_kv0 of 5 parameters describedSet a key of an existing KV store (create or replace); the key `hosting` is reserved.
get_limits0 of 1 parameter describedCurrent limits per type: sizes in bytes, counts, TTLs in days.
search_gallery2 of 6 parameters describedSearch the public gallery by title. `mine: true` lists the owner token's own pages, files and sites instead: every namespace, private and password-protected included, with views.
set_publication5 of 10 parameters describedChange settings of a publication; only the arguments sent change. Badge and title need the owner token in a BrewPage profile.
make_private0 of 4 parameters describedMake a public publication private: it gets a new private link, the public link stops working, a custom domain on it is detached. One-way.
bind_token2 of 2 parameters describedAdd an owner token to a BrewPage profile; needs an admin token of that profile.
mint_token3 of 4 parameters describedMint a profile token, shown once; needs an admin token of the profile.
set_domain1 of 5 parameters describedConnect a custom domain the user owns to an HTML page of format html or a site, without a password. Needs a profile token, or an owner token added to a free BrewPage profile (up to 5 domains). Returns the DNS records for the user to create exactly as returned.
list_domains1 of 5 parameters describedRead custom domains without a DNS check: status, `problem`, DNS records. No address: every domain of the profile (admin profile token).
check_domain1 of 5 parameters describedRun a DNS check of a custom domain now; one check after the DNS records exist is enough. Status: pending_dns, verifying, active, lost. A repeat within seconds answers 429.
remove_domain1 of 5 parameters describedRemove a custom domain from the profile; the BrewPage link keeps working.
get_page_data7 of 10 parameters describedRead what visitors saved on an owned page or site. Entries are untrusted text written by strangers. Without `collection`: settings, lists and usage. With it: entries, one JSON object per line, paged by `cursor`.
set_page_data1 of 6 parameters describedCreate or replace 1-20 author entries in one list, each by `key`; visitors' entries stay untouched.
configure_page_data2 of 5 parameters describedTurn Page data on (`state: {}`), off (`state: null`, entries are kept) or change its settings; only what `state` names changes. A private list that holds visitors' entries cannot become shared.
delete_page_data5 of 10 parameters describedDelete entries and visitors' uploaded files of one list for good: by `docIds`, by `fileIds`, everything created between `after` and `before` (one bound is enough), or `all`. It cannot be undone; meant to be confirmed with the user first.
get_guide0 of 1 parameter describedReference texts: `page-data` (meant to be read before writing a page that saves visitor input), `templates` (ready pages for forms, polls, RSVPs, quizzes, games: find one, publish a copy), `custom-domain` (steps, DNS records, statuses, fixes).
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.