delete_resource
Delete a BrewPage resource (HTML page, KV store, JSON collection, or file) using the owner token.
LABSCO SUMMARY
The owner token is the whole access model — no account, but nothing to recover either.
Publishing needs no identity at all, and the token returned at creation is what proves ownership afterwards: update in place, delete, or list what is yours. Lose it and the page stays up until its TTL expires. That trade is what makes this useful for an agent that needs to hand a human a link right now — a report, a preview, a JSON payload — without a deployment pipeline existing first.
What it is
A client for BrewPage, an instant hosting service. One call publishes content and returns a public HTTPS URL plus an owner token; the token is what lets you update or delete that resource later.
What you get
- HTML or Markdown published to a public URL, with optional password, a time-to-live in days, a filename and an opt-in top toolbar — publish_html
- A whole site published from an array of path-and-content files, with an entry point you can override — publish_site
- An existing page updated in place, and a multi-file site fully replaced at the same URL, with the uploaded bundle becoming the complete new file set — update_html, republish_site
- A file uploaded by URL and rehosted — publish_file
- JSON documents published, fetched and updated — objects, arrays or JSON-encoded strings — publish_json, get_json, update_json
- A key/value store created and then read and written key by key — publish_kv, set_kv, get_kv
- Published pages fetched back, including password-protected ones — get_page
- Anything you own deleted with its owner token — delete_resource
- The public gallery searched, optionally scoped to your own resources with the owner token — search_gallery
- Platform-wide usage statistics, with the day boundary shifted to an IANA timezone if you need it — get_stats
Requirements
No account and no API key — publishing is a single call and the owner token comes back with the URL, so keep it if you intend to update or delete. Run npx -y brewpage-mcp over stdio. BREWPAGE_URL overrides the API base, which defaults to https://brewpage.app. Resources are addressed by namespace and id.
Setup effort
One command — npx -y brewpage-mcp
USE CASES
01
Handing someone a link to something the agent just produced
Publish the HTML or Markdown and pass on the URL, with a TTL so it does not live forever.
02
Putting up a small multi-page site
Publish the files as a bundle with an entry point, then replace the whole set in place when it changes.
03
Sharing structured data instead of pasting it
Publish the JSON to a URL, then update the same document as the data changes.
04
Keeping small state between sessions or between agents
Create a key/value store, then set and read individual keys against it.
05
Sharing something only one person should see
Publish with a password, and fetch it back with the same password when you need the content.
06
Clearing up what you published earlier
Find your own resources with the owner token, then delete the ones that are finished with.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_json
Fetch a published BrewPage JSON document by namespace and ID.
get_kv
Fetch a value from a BrewPage KV store by namespace, ID, and key.
get_page
Fetch a published BrewPage HTML page content by namespace and ID.
get_stats
Get BrewPage platform-wide usage statistics including page count, file count, and storage usage. Counts use disjoint split: alive_public + alive_private + deleted == total. Optional tz shifts the 'today' boundary to the given IANA zone (default UTC).
publish_file
Upload a file to BrewPage via URL. Returns a public URL and owner token.
publish_html
Publish HTML or Markdown content to BrewPage. Returns a public URL and owner token. Supports password protection, custom TTL, optional filename, and an opt-in top toolbar (showTopBar).
publish_json
Publish a JSON document to BrewPage. Accepts a JSON object, array, or a JSON-encoded string. Returns a public URL and owner token.
publish_kv
Publish a key/value entry to BrewPage. Creates a KV store; the entry is addressed by (namespace, id, key). Returns a public URL and owner token.
publish_site
Publish an HTML site to BrewPage. Single-page: pass entryContent. Multi-page: pass files (array of {path, content}). Optional entry overrides default index.html.
republish_site
Republish (full-replace) an existing multi-file BrewPage site in place at the SAME URL/ID. Requires owner token. The uploaded bundle becomes the complete new file set — files absent from it are removed, new files added, matching files overwritten. Single-page: pass entryContent. Multi-page: pass files (array of {path, content}). Optional entry overrides the default index.html.
search_gallery
Search the BrewPage public gallery. Optional filters: text query, pagination, sort, and 'mine' (owner-scoped, requires owner token).
set_kv
Set or update a key in an existing BrewPage KV store. Requires owner token.
update_html
Update an existing BrewPage HTML/Markdown page. Requires owner token. Returns the updated page metadata.
update_json
Update an existing BrewPage JSON document. Requires owner token. Accepts a JSON object, array, or a JSON-encoded string.
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. republish_site is newer than the documentation, which covers fourteen tools and gives no parameters for it.
Requires
npx on PATH
Where it runs
All 4 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y brewpage-mcpMCP Clients
Claude Desktop, Claude Code, Cursor, Cline
JSON
{
"mcpServers": {
"brewpage": {
"command": "npx",
"args": [
"-y",
"brewpage-mcp"
]
}
}
}
