Publee Dev MCP logo

Publee Dev MCP

by publee-dev

Publishes HTML or static files to shareable Publee URLs, with optional persistent hosting and in-place updates.

Install Publee Dev 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": {
    "publee-dev-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "github:publee-dev/mcp"
      ],
      "env": {
        "PUBLEE_API_TOKEN": "YOUR_VALUE_HERE",
        "PUBLEE_API_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

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

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Publish generated HTML or static file trees through the publee-dev/mcp MCP server and receive a shareable .publee.site URL. Its `publee_publish` tool supports anonymous publishing without an account, while an API token enables indefinite retention, same-URL updates, and additional visibility modes. Use it when an agent needs to show a generated page or static artifact without a build pipeline or separate hosting setup. The repository provides a local stdio server, and Publee also offers a hosted Streamable HTTP endpoint.

Use cases

  • Publish an AI-generated landing page for review
  • Share a generated HTML report through a public URL
  • Host static files without configuring a web server
  • Update an existing shared page while keeping its URL
  • Restrict access to a password or member list

Key features

  • Publish HTML documents
  • Publish static file trees
  • Anonymous seven-day hosting
  • Token-based persistent hosting
  • In-place updates with stable URLs
  • Configurable visibility modes

Tools1

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

Self-reported~22 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 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · github:publee-dev/mcp (npm)

Adoption & maintenance

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

Last commit2mo agoMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.

How Publee Dev MCP works

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.

Reviews

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

Frequently Asked Questions about Publee Dev MCP

publee-dev/mcp is an MCP server that connects AI tools to Publee for publishing HTML documents or static file trees. Its main tool, `publee_publish`, returns a shareable `.publee.site` URL and supports anonymous seven-day publishing, token-based persistent hosting, visibility settings, and in-place updates.

Run it as a local stdio server with `npx -y github:publee-dev/mcp` in your MCP client configuration. Set `PUBLEE_API_TOKEN` when authenticated publishing is needed, or omit it for anonymous publishing. You can also configure the hosted endpoint at `https://publee.app/api/mcp` instead of running the repository locally.

Yes, publee-dev/mcp works with Cursor. The README names Cursor as a supported client for the hosted MCP endpoint and provides documentation for its configuration. Cursor can connect to the hosted Streamable HTTP endpoint, while clients that support local stdio can run the repository command.

Use the `slug` parameter together with `overwrite: true`, and provide an API token. This updates an existing token-owned site in place rather than creating another URL. Anonymous publishing does not provide the authenticated persistence and update behavior described for token-based sites.

Yes, anonymous publishing is supported by omitting `PUBLEE_API_TOKEN`. Anonymous sites expire after seven days, and the tool result includes a claim URL for transferring the site to an account. A token is required for indefinite retention, in-place updates, and the additional authenticated visibility options.

Related MCP servers

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 PreviewPublee Dev MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/publee-dev-mcp?style=directory)](https://allmcps.com/mcp/publee-dev-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/publee-dev-mcp"><img src="https://allmcps.com/api/badge/publee-dev-mcp?style=directory" alt="Publee Dev MCP on AllMCPs" /></a>