# publee-dev/mcp [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/publee-dev/mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/publee-dev-mcp

## Description
Publish AI-generated HTML or static files to a shareable .publee.site URL in seconds. Works anonymously with zero setup (7-day retention); an API token adds permanent hosting, in-place updates that keep the same URL, and limited-sharing visibility (password, members-only).

## Tools
Capabilities this server exposes over MCP:

- **publee_publish** — Publish a single HTML document (`html`) or a static file tree (`files`) and

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp": {
    "command": "npx",
    "args": ["-y","github:publee-dev/mcp"],
    "env": {
      "PUBLEE_API_TOKEN": "",
      "PUBLEE_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `PUBLEE_API_TOKEN`, `PUBLEE_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What publee-dev/mcp MCP server does

The publee-dev/mcp MCP server sends generated web content to Publee and returns a URL under `.publee.site`. It accepts either one HTML document or a static file tree, so an agent can publish a complete page or a small collection of assets without setting up a build process or web host.

Publishing can be anonymous. Anonymous sites remain available for seven days, and the result includes a claim URL that can be used to transfer the site to an account. Supplying a Publee API token associates the publication with an account and makes it persistent indefinitely, including on the free plan.

The `publee_publish` tool also supports visibility controls. Available values include `public`, `password`, `private`, `workspace`, and `members`. Password-protected and members-only publishing require the relevant account capabilities; member access can be specified with email addresses.

## How it works

The server exposes one documented tool: `publee_publish`. A caller provides `html` for a single document or `files` for a static file tree, along with optional metadata such as `title`, `visibility`, and `noindex`. The tool responds with the published site URL.

For revisions, provide a `slug` and set `overwrite` to `true`. This requires an API token and updates the existing site instead of creating a new URL. The `spaMode` option is available for single-page application behavior. The publee-dev/mcp MCP server is therefore suited to agents that need to publish an initial result and later replace it at the same address.

## Setup and configuration

The repository supports local MCP clients that can launch a stdio process. A typical configuration runs `npx -y github:publee-dev/mcp`. `PUBLEE_API_TOKEN` is optional: leave it out for anonymous seven-day sites, or set it to a token issued through Publee for persistent sites and authenticated features.

`PUBLEE_API_URL` defaults to `https://publee.app` and can override the API origin for development. The server can also be used without a local installation through Publee's hosted endpoint at `https://publee.app/api/mcp`, which uses OAuth. The hosted configuration is documented for Claude Desktop, Cursor, and other MCP clients.

## Tools and capabilities

- Publish one HTML document with `html`.
- Publish a static file tree with `files`.
- Set a page title and visibility mode.
- Add a password or member email list where supported.
- Preserve a URL when updating a token-owned site with `slug` and `overwrite`.
- Enable SPA handling or request `noindex` behavior.

## Limitations and notes

Anonymous publications expire after seven days and are not equivalent to permanent hosting. Persistent storage, in-place updates, and additional visibility options require an API token. The local repository mode is intended for clients that support stdio, while the hosted endpoint uses Streamable HTTP and OAuth. The publee-dev/mcp MCP server publishes through Publee; it does not provide a separate build system or general-purpose hosting configuration.

_Full upstream README: https://allmcps.com/mcp/publee-dev-mcp/readme_