artifact-site

artifact-site

English | 简体中文 | 日本語 | Deutsch | Français | Español

There are now so many AI agents to choose from, but their output is scattered across your computer, chat histories and different platforms’ clouds, making it hard to organize, share and revisit.

artifact-site is a self-hosted workspace for individuals and teams, similar to Claude Artifacts or OpenAI Sites. Your various agents create the work; artifact-site brings it together, turning pages and documents into links for sharing, comments and feedback, access control and version history. The agents you already use can keep editing, publishing, searching and updating that work through the CLI or MCP.

You can self-host artifact-site or use the cloud version hosted by Lexmount.

[Use the cloud version](https://yours.lexmount.com/artifact-site) — hosted by Lexmount, with no deployment required. Drag and drop a file to publish it and get a shareable link. Upload without signing in, or sign in with Google or GitHub to keep your sites, organize them in folders and control who can open each link.

Anonymous uploads expire after a few days.

Drop a file, get a link, share it. View your published work online and choose who can open it in the sharing settings.

Why artifact-site

• Keep work in one place. Organize pages and documents in folders and find them with full-text search, including Chinese. Team members and agents can find the work they have permission to access.
• Drop it in and share it. Upload HTML, a build folder, a ZIP or a document to get a link. Large sites upload in chunks. Share with everyone, signed-in users, named people or passcode holders.
• Keep improving published work. Edit HTML text or source in the browser, or let an agent update the whole site. Each change keeps a version, with rollback and the option to save a copy.
• Let agents pick up where they left off. Publish and update through the guide, CLI or MCP, then search by content and read extractable text. For example, find a previous report and update it at the same address for your team to view.

How it compares

¹ Office online preview requires Gotenberg. artifact-site hosts finished files; it does not run application backends or build jobs.

Claude Artifacts and ChatGPT Sites combine creation and hosted sharing. artifact-site complements those workflows with a shared home on your own infrastructure for pages and documents produced by different tools.

Product scope and sharing vary by plan and evolve; see the official Claude Artifacts and ChatGPT Sites guides.

Contents

• What you can publish
• Quick start (local deployment)
• Connect a coding agent
• Deploy for your team
• How it works
• Documentation
• Contributing
• License

What you can publish

Build web projects into static files before uploading; the platform does not run application backends or build jobs. PDF and Office documents do not support visual HTML editing, and scanned images are not automatically OCRed.

Hosted pages run in a sandbox and cannot use the platform's login session. External API connections require an origin allowlist. See the runtime limits and security design.

Quick start (local deployment)

You can use the cloud version without installing anything. To deploy locally, run the three commands below. You need Git, Make, Bash, Docker 24+ and the Compose plugin 2.24+. On macOS, use Docker Desktop; on Windows, run the commands inside WSL2 with Docker Desktop’s WSL integration enabled. No Node installation, domain or identity provider is needed.

git clone https://github.com/lexmount/artifact-site.git && cd artifact-site

cp .env.example .env make build up

Once started, open http://127.0.0.1:4300 and drop in HTML, a static site folder or a PDF to view your work. New sites are private by default; change main-link access in Sharing before sending it to someone else.

The first run downloads dependencies and builds the image, then starts the app and Postgres. Use these commands in a fresh clone. The service is local-only by default; make down stops it and retains data. To make it reachable by your team, follow Deploy for your team.

Need a file to try? Create a sample page

printf '<!doctype html><meta charset="utf-8"><title>Hello</title><h1>Hello, artifact-site!</h1>' > hello.html

Drop hello.html onto the home page (or choose Upload). You should see “Hello, artifact-site!”. Copy a link from the sharing settings; local-deployment links only open on the same machine.

Connect a coding agent

Choose the entry point that fits your agent:

• Skill: npx skills add lexmount/artifact-site — install the agent skill and give your agent your server URL.
• CLI: npm install -g @artifact-site/cli — requires Node 24+; use the commands below.
• MCP: https://your-server/mcp — connect ChatGPT, Claude or another MCP client through the server’s OAuth sign-in; no CLI installation required. A client that only starts local MCP servers can run the CLI’s artifact-site mcp instead.

CLI and MCP create private artifacts by default, without independent share links. Use artifact-site visibility unlisted or MCP artifact_site_set_visibility when the user asks to share the main link.

Or let your coding agent do it. With the agent guide ( /for-agents.md ), the CLI or the MCP server, "publish this and give me a link" is one instruction — and the site can be updated, searched and read the same way.

Give this instruction to Claude Code, Cursor, Codex or another coding agent that can read URLs, using a server address it can reach. The home page also provides a copy button with your server address filled in:

Publish this project's output to artifact-site. Publishing guide: https://your-server/for-agents.md

CLI examples (login requires OIDC):

artifact-site login --base https://your-server        # one-time device sign-in

artifact-site publish dist/ --title "Q3 dashboard" # publish and return links artifact-site find "quota" # search by content artifact-site read YOUR_SITE_SLUG # replace with a site slug to read its text

Authentication details

Open Agent guide on your deployment to choose the prompt, CLI or MCP path. /for-agents#cli and /for-agents#mcp provide server-specific commands, authentication steps and client configuration. Remote MCP authenticates every request: ChatGPT, Claude and other OAuth-capable clients sign in through the server's own consent page, other clients carry a personal token. Publishing is private by default; open main-link access explicitly with the visibility operation. Advanced independent links are opt-in.

Team deployments with OIDC support device sign-in approval; the anonymous local setup above does not require it. The agent follows the guide and the server's publishing policy to choose authentication. A cloud agent cannot directly reach 127.0.0.1 on your computer.

The login example requires OIDC. Remote MCP is a separate, complete entry point at https://your-server/mcp: no CLI installation is required. ChatGPT, Claude and any client that implements MCP authorization connect with the address alone and sign in through the server's OAuth consent page; for other clients, the deployment's /for-agents#mcp page creates a personal token and copies the authenticated configuration. It supports publishing, updating, search, read, sharing, versions, export and deletion, including binary files and directory uploads through MCP tools.

See CLI commands and remote MCP setup and tools.

Deploy for your team

Start from .env.example and follow SELFHOST.md for a production deployment. Use a stable public address for ARTIFACT_PUBLIC_URL: sign-in callbacks, request-origin checks and the address given to agents derive from it:

• Set a reachable ARTIFACT_PUBLIC_URL and configure a reverse proxy, or set ARTIFACT_WITH_CADDY=on with ARTIFACT_DOMAIN to enable Caddy and automatic certificates.
• Choose a publishing policy. login requires OIDC; token serves scripts or agents with a Bearer token; open lets anyone who can reach the service publish and suits trusted internal networks. Anonymous publishing supports separate quotas and expiry.
• Connect Google or an OIDC provider such a