Log inSubmit server
BrewPage MCP logo

BrewPage MCP

Publish and manage BrewPage HTML, sites, files, JSON, and KV data through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install BrewPage MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "brewpage-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brewpage-mcp@1.15.1"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

BrewPage MCP MCP server connects AI assistants to BrewPage for publishing HTML, Markdown, static sites, files, JSON documents, and key-value data. Its tools return public links and owner tokens, then support retrieval, in-place updates, replacement, and deletion. Use it when an agent needs to share generated artifacts or persist lightweight structured data without signup or API-key setup. It also provides gallery search and platform usage statistics.

Use cases

  • Publish an AI-generated HTML report and return its stable URL
  • Deploy a generated multi-file static site
  • Store JSON state between agent interactions
  • Upload a downloadable file or artifact
  • Update a published page without changing its URL

Key features

  • HTML and Markdown publishing
  • Multi-file static site deployment
  • JSON document and KV storage
  • Owner-token resource management
  • Gallery search and platform statistics
  • File uploads with public URLs

Tools16

What BrewPage MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.9k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 45d

What it can do

From the 16 tools this server returned when we ran it.

Can delete or modify data · 1Handles credentials · 11Makes network requests · 8Read-only tools · 15
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age198 days
Maintainers1

Observed 2026-10-16 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 20h ago via OSV.dev · brewpage-mcp@1.15.1 (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads2.5kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed16Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How BrewPage MCP works

What BrewPage MCP MCP server does

BrewPage MCP MCP server exposes BrewPage's hosting and data API through typed MCP tools. Agents can publish HTML or Markdown pages, upload files by URL, deploy single-page or multi-file sites, store JSON documents, and create key-value stores. Creation operations return a public URL and an owner token for later management.

The service supports both content delivery and lightweight persistence. Published pages and sites can be fetched, JSON and KV values can be read back, and existing resources can be changed or removed without an account. BrewPage publications can use public or private namespaces, while password protection is available for supported content.

How it works

An assistant calls a publish tool with content or resource details. BrewPage returns an identifier, link, expiry information, and an owner token. The assistant should retain that token when it needs to update or delete the resource later. Content updates preserve the existing URL.

HTML publishing accepts raw HTML or Markdown and can configure password protection, TTL, an optional filename, and the top toolbar. Site publishing accepts an entry document for a single-page site or an array of paths and contents for a multi-file site. Republished sites fully replace the prior file set at the same URL, so omitted files are removed.

JSON tools accept an object, array, or JSON-encoded string. KV data is addressed by namespace, store ID, and key. Gallery search supports text, pagination, sorting, and an owner-scoped mode that requires an owner token. Statistics include page, file, and storage counts, with an optional IANA time zone for the daily boundary.

Tools and capabilities

  • Publish and retrieve HTML or Markdown pages.
  • Upload files and publish static sites with multiple files.
  • Publish, fetch, and update JSON documents.
  • Create and modify namespace-based key-value stores.
  • Update HTML content while retaining its URL.
  • Replace a multi-file site in place.
  • Change hosting mode for eligible new publications.
  • Delete resources with an owner token.
  • Search the public gallery and inspect platform statistics.

Limitations and notes

No signup or API key is required to create publications. Unlisted resources are not indexed, but anyone with their link can open them; public resources may appear in the gallery and sitemap. Password-protected publications, JSON, and KV resources are not listed.

HTML pages support up to 5 MB. Sites allow up to 200 files, 5 MB per file, and 20 MB total. JSON documents support up to 1 MiB, KV stores allow up to 1,000 keys, and file uploads support up to 5 MB, or 20 MB for video. Default publication lifetime is 15 days, with an ordinary maximum of 30 days; callers should use the returned expiration time.

Owner tokens control updates and deletion, so they should be treated as secrets. Rate limits vary by operation and visibility. Clients should handle HTTP 429 responses and the Retry-After header. Hosting changes apply only to eligible new public non-site publications, and a 409 conflict requires reloading before retrying.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about BrewPage MCP

BrewPage MCP is an MCP server that connects AI assistants to BrewPage hosting and storage. Its main tools publish HTML, Markdown, sites, files, JSON, and KV data, then retrieve, update, replace, or delete those resources. It also searches the public gallery and returns platform usage statistics.

Use the BrewPage MCP package and configure it as an MCP server for your client. The service itself requires no signup or API key to create publications, and the repository publishes the server as the brewpage-mcp package.

Yes, BrewPage MCP works with Cursor because it is an MCP-compatible server. Cursor can call its publishing, storage, retrieval, update, deletion, gallery, and statistics tools when the server is configured in the client.

Use update_html for an HTML or Markdown page, update_json for a JSON document, set_kv for a key-value entry, or republish_site for a complete multi-file site replacement. These operations require the owner token returned when the resource was created.

No, creating BrewPage publications does not require signup or an API key. Keep the returned owner token to manage or delete resources; optional account sign-in can help preserve access to pages and tokens.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBrewPage MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/brewpage-mcp?style=directory)](https://allmcps.com/mcp/brewpage-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/brewpage-mcp"><img src="https://allmcps.com/api/badge/brewpage-mcp?style=directory" alt="BrewPage MCP on AllMCPs" /></a>