Server facts
brewpage-openapi MCP Server
Project
- Author
- kochetkov-ma
- Repository
- github.com/kochetkov-ma/brewpage-openapi
- Website
- brewpage.app
- License
- Not specified
- Category
- Files & Documents
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Overview
BrewPage content can move from an AI assistant into hosted pages, downloadable files, structured documents, or key/value storage through brewpage-openapi. HTML and Markdown publishing includes options for a password, expiration period, filename, and top toolbar. Site publishing accepts either a single page or a collection of paths and content, with a configurable entry file. File uploads take a source URL, while JSON publishing accepts objects, arrays, or encoded JSON strings. Publishing returns a public link together with an owner token; BrewPage does not require signup.
The management tools cover reading back pages, JSON documents, and stored values, plus changing existing pages, documents, and keys. Site replacement keeps the existing address but replaces the complete file set, removing files omitted from the new upload. Updates and deletion rely on the owner token, which cannot be recovered if lost. Public-gallery searches support text, sorting, pagination, and owner-scoped filtering. A separate statistics tool reports platform page and file counts alongside storage use, with an optional time zone for daily boundaries. The MCP connection uses stdio.
brewpage-openapi setup notes
- brewpage-openapi records stdio only; confirm a network transport upstream before planning remote access.
- brewpage-openapi has no recorded license; confirm reuse terms in its repository.