# share

> Static hosting for AI assistants: publish HTML over the Model Context Protocol and get back a live, verified, versioned URL.

share is a remote MCP server. An assistant declares the files it wants to publish, uploads the
bytes to the edge, and the server verifies every stored object against that declaration before
anything is served. Publishing is one tool call; rolling back is another.

## MCP

- [MCP endpoint](https://share-flame-nine.vercel.app/api/mcp): The whole interface. Streamable HTTP transport, OAuth 2.1 with dynamic client registration. Tools: prepare_deployment, finalize_deployment, publish_inline, list_sites, get_site, rollback_site, delete_site.
- [Connect an assistant](https://share-flame-nine.vercel.app/guides#connect): Add the endpoint above as a custom connector, sign in once, and publishing works from any chat.
- Resources: resources/list returns the MCP App view (ui://share/view.html) and every site you have published, addressed by its own public URL. resources/read on a site URI returns the bytes the edge is actually serving.
- MCP App: every tool declares _meta.ui.resourceUri, so a host that supports MCP Apps (SEP-1865) renders the published page itself, live, beside the tool result rather than a wall of text.

## Docs

- [Guides](https://share-flame-nine.vercel.app/guides): Connect an assistant on mobile, publish a first site, roll a publish back, and what to do when something looks wrong.
- [Security](https://share-flame-nine.vercel.app/security): The manifest, the signed upload grant, SHA-256 verification at finalize, the content-type allowlist, what the server can and cannot see, and the limits that are not fixed.
- [Pricing](https://share-flame-nine.vercel.app/pricing): Free while it is new. Ten sites per account, 25 MB per site, no paid plan yet.
- [Support](https://share-flame-nine.vercel.app/support): Contact address, realistic response times, and the takedown process.
- [Privacy](https://share-flame-nine.vercel.app/privacy): What is collected, where it is stored, how long it is retained, and how to delete it.
- [Terms](https://share-flame-nine.vercel.app/terms): Acceptable use, content ownership, suspension and liability.

## How publishing works

- Declare: prepare_deployment takes {path, size, sha256, contentType} for every file and stores it as the version's immutable manifest.
- Upload: the server returns one short-lived signed grant per file. The edge recomputes SHA-256 over the body and refuses to write a mismatch.
- Finalize: finalize_deployment compares every stored object to the manifest. All match, or the version is discarded — there is no partial publish.
- Inline: publish_inline sends small text files (1 MB total) in a single call for assistants with no sandbox network access. Same manifest, same verification.

## Optional

- Published sites are served one origin per site, for example https://your-slug.uholdco.space/, from an origin separate from this app.
- Content types are an allowlist, not a blocklist. HTML, CSS, JavaScript, JSON, text, PNG, JPEG, GIF, WebP, AVIF, ICO and WOFF are allowed; SVG, PDF, video and WebAssembly are not.
- A publish can take up to about a minute to be visible from every edge location.
- There is no REST API and no OpenAPI document. If one is added it will be listed here.