Artifact Server — open-source Claude Code artifacts

Open source · self-hostable

Artifact Server gives people and agents one place for the files they create during product development. Publish, review, comment on, version, and share the same work. The built-in MCP server gives agents direct access.

Run it locally Deploy for a team

RELEASE 04 · READY FOR REVIEW

Dev work worth keeping.

ALSKComments 3

1Keep this tied to the exact version.

The new explanation is clear. The diagram should name the content boundary too.

2Ready for the agent.

Send this thread with the artifact context and let it close the loop.

3Swap the hero image for the new render.

The one in v3 is the old palette.

Why Artifact Server

Own your team's SDLC outputs

Product teams create plans, mockups, prototypes, and code reviews as HTML, images, and video. These files often end up scattered across tools. Artifact Server keeps them organized, reviewable, and under your control.

Integrated with Agents

Agents publish through MCP or the Agent Skill. People use the CLI or browser. Each upload can contain one file or a complete site.

/artifact-server upload that HTML design doc

Keep immutable versions.

Every save creates an immutable version inside a project. Stable artifact links open the current version. Exact version links never change.

Project → Artifact → Version

Review with your team.

Comments stay attached to the exact version and selected content. Share a review link so everyone can discuss the same work.

Review link → Team feedback → Next version

Built for AI agents

Comment threads with connected agents.

Any MCP client can publish, organize, review, comment on, and share versioned artifacts through the built-in server. Pi, OpenCode, and Claude Code can also connect as live agents. One click sends every open comment to the running session. The agent can reply, resolve comments, and publish the next version without copying feedback into chat.

Connect a coding agent

Comments 3Pi · replying

1Name the content boundary in the diagram.

Added the isolated content origin to the diagram and the caption. Resolved.

2The install command is stale.

Updated to the current command in both places. Resolved.

3Tighten the second paragraph.

Sent · replying…

Yours to run

Run it on a laptop or deploy it for a team.

Local

Run with loopback-only owner access and no sign-in. Store SQLite data and files on your machine.

git clone … && pnpm dev

Cloudflare

Deploy with Workers, D1, R2, private team authentication, and isolated content domains.

Workers · D1 · R2Versioned and Git-backed with:Cloudflare ArtifactsClosed beta

Your infrastructure

Deploy with Docker Compose, Kubernetes, AWS, or Google Cloud. The storage provider does not change product behavior.

Compose · Kubernetes · AWS · Google Cloud

Every remote deployment requires one trusted application origin and one isolated wildcard content domain.

The deployment guide covers shared requirements, storage choices, authentication, and backups.

Choose a deployment

Get started

Start with a local installation.

Get started locally Star on GitHub