BrewPage MCP
Publish HTML, Markdown, JSON, KV data, and files to brewpage.app straight from your agent—no separate signup flow in the README pitch.
Overview
BrewPage MCP is a MCP server for the Launch phase that publishes HTML, Markdown, KV, JSON, and files to brewpage.app from your AI assistant.
What is this MCP server?
- Publish HTML, Markdown, KV, JSON, and arbitrary files to brewpage.app
- Documented no-signup publishing story for AI assistants
- stdio npm brewpage-mcp v1.3.2 with optional BREWPAGE_URL override
- Defaults API base to https://brewpage.app
- MCP server lives in brewpage-openapi repo mcp-server subfolder
- Package version 1.3.2 with stdio transport
- Optional BREWPAGE_URL env default https://brewpage.app
- npm identifier brewpage-mcp on registry.npmjs.org
Community signal: 1 GitHub stars.
What problem does it solve?
You have agent-generated pages or data but waste time copying files into hosting dashboards just to share a link.
Who is it for?
Indie builders who live in Claude Code or Cursor and want instant public links for landings, docs, or JSON without standing up a full site.
Skip if: Teams needing custom domains, complex RBAC, or long-term CMS workflows on their own cloud accounts.
What do I get? / Deliverables
Your agent can push content to a live brewpage.app URL in one MCP call so you ship shareable assets the same session you wrote them.
- Live brewpage.app URLs for published HTML, Markdown, JSON, or KV payloads
- Agent-driven file uploads without a separate signup flow described in catalog copy
- Repeatable publish step you can script from agent sessions
Recommended MCP Servers
Journey fit
Once something works, solo builders need frictionless URLs to share demos, docs, and landing snippets—launch distribution is the natural home. Distribution covers getting artifacts in front of users and collaborators; BrewPage is a one-shot publish channel from the agent.
How it compares
Hosted publish MCP integration, not a static-site generator skill or full deployment platform.
Common Questions / FAQ
Who is BrewPage MCP for?
Solo and indie builders who use MCP agents and want to publish HTML, Markdown, KV, JSON, or files to brewpage.app without a manual upload step.
When should I use BrewPage MCP?
Use it at launch (or quick validate demos) when you need a shareable URL for a page, dataset, or file generated during an agent session.
How do I add BrewPage MCP to my agent?
Install brewpage-mcp from npm, add a stdio MCP server block in your client, and optionally set BREWPAGE_URL if you are not using the default https://brewpage.app API.