# AI use cases for Artifact Server (plannotator/artifact-server) Repo: [plannotator/artifact-server](https://github.com/plannotator/artifact-server) | Use cases: 4 | Page: https://dedupedai.com/use-cases/plannotator-artifact-server/ Artifact Server is an open source, self-hostable place to publish, review, comment on, version, and share HTML, images, and video artifacts, with a built-in MCP server for agents. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Publish an agent's design doc for full-screen review: https://dedupedai.com/use-cases/plannotator-artifact-server/agent-publishes-design-doc-for-review/ - Run a private artifact server on your laptop: https://dedupedai.com/use-cases/plannotator-artifact-server/run-artifact-server-locally-for-one-developer/ - Host a private artifact hub for your product team: https://dedupedai.com/use-cases/plannotator-artifact-server/deploy-private-artifact-hub-for-team/ - Run the full check gate before handing off changes: https://dedupedai.com/use-cases/plannotator-artifact-server/verify-artifact-server-changes-before-handoff/ ## How to publish an agent's design doc for full-screen review with Artifact Server Repo: [plannotator/artifact-server](https://github.com/plannotator/artifact-server) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Let Claude Code upload an HTML design doc and return a review link you can comment on. **Who it is for:** A developer using Claude Code to draft a plan or design doc who needs teammates to review it without it getting lost in a chat log. **The problem:** Agent-made HTML plans and mockups scatter across chats and local folders, so reviews and comments have no stable home. **The outcome:** The agent uploads the HTML file, returns a full-screen review link, and the review thread stays attached to that artifact. ### Steps 1. Start a local server, following the steps in the local run use case, or open a remote Artifact Server you already have access to. 2. Run `artifactserver connect`. 3. Run `npx skills add plannotator/artifact-server`. 4. In Claude Code, send `/artifact-server upload that HTML design doc`. 5. Open the full-screen review link the agent returns and leave a comment to test the review flow. ### Prompt to paste into your agent ```text In the plannotator/artifact-server repo setup, use the Artifact Server Skill to upload the HTML file at as a new artifact. Expected output: the full-screen review link returned first. Verify that the link opens and shows the uploaded document. ``` ### Caveat The README says the Claude Code live session delivery needs a research-preview development flag and, on managed plans, an organization policy, so the basic skill upload is the path to rely on. Risk, remote script: The skill install command pulls the plannotator/artifact-server skill from GitHub, so review its contents before you run it in an environment with access to real project files. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/plannotator-artifact-server/agent-publishes-design-doc-for-review/ ## How to run a private artifact server on your laptop with Artifact Server Repo: [plannotator/artifact-server](https://github.com/plannotator/artifact-server) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Start Artifact Server from source so one developer can store and review artifacts locally. **Who it is for:** A solo developer or agent builder who wants a private place for AI-made artifacts before deciding on a team deployment. **The problem:** Artifacts from agents pile up in local folders with no review, versioning, or sharing workflow. **The outcome:** A local Artifact Server runs on a printed URL, with metadata in SQLite and files on disk, and owner access from the same loopback origin. ### Steps 1. Run `git clone https://github.com/plannotator/artifact-server.git`. 2. Run `cd artifact-server`. 3. Run `pnpm install`. 4. Run `pnpm dev`. 5. Open the URL printed in the terminal. ### Prompt to paste into your agent ```text Clone https://github.com/plannotator/artifact-server.git into a local folder, then run pnpm install and pnpm dev. Expected output: a printed local URL. Verify that the page loads in a browser on the same machine. ``` ### Caveat The README says running from source needs Node.js 24.12 or newer and pnpm 10.34.3, and local mode grants owner access only from the same loopback origin, so it is not a shared server for other people. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/plannotator-artifact-server/run-artifact-server-locally-for-one-developer/ ## How to host a private artifact hub for your product team with Artifact Server Repo: [plannotator/artifact-server](https://github.com/plannotator/artifact-server) | Difficulty: Advanced | Time: 4 hours | Basis: From the README Deploy Artifact Server on a hosting target your team already uses for shared review. **Who it is for:** A tech lead or platform engineer whose product team needs one shared, self-hosted place for agent-made plans, mockups, and reviews. **The problem:** Teams that use AI agents produce artifacts faster than they can organize, review, and share them, and hosted platforms lock the files in. **The outcome:** A team-wide Artifact Server with one trusted application origin and one isolated wildcard content domain, reachable by the team and agents through MCP. ### Steps 1. Read the deployment guide at docs/deployment.md for shared requirements, storage choices, authentication, and backups. 2. Choose a deployment target from the table: Cloudflare, Compact Compose, External-storage Compose, Kubernetes, AWS, or Google Cloud. 3. Follow that target's guide, such as deploy/cloudflare/README.md or packaging/helm/artifact-server/README.md. 4. Configure one trusted application origin and one isolated wildcard content domain. 5. Connect agents with the MCP guide at docs/mcp.md and test an upload from one team member. ### Prompt to paste into your agent ```text Using the plannotator/artifact-server deployment guide, pick the target and list the setup steps it needs. Expected output: a checklist of requirements, origins, and storage choices. Verify that the checklist includes both the trusted application origin and the wildcard content domain. ``` ### Caveat The README says Cloudflare Artifacts for Git history needs closed beta access and is off by default, and Azure Blob Storage is a preview adapter that has not passed live Azure qualification. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/plannotator-artifact-server/deploy-private-artifact-hub-for-team/ ## How to run the full check gate before handing off changes with Artifact Server Repo: [plannotator/artifact-server](https://github.com/plannotator/artifact-server) | Difficulty: Intermediate | Time: 45 minutes | Basis: From the README Run the project's checks and iteration gate on a local checkout before sending a change for review. **Who it is for:** A contributor or an AI coding agent that has edited the Artifact Server source and must prove the change is safe to hand off. **The problem:** Changes to a multi-part project with specs, conformance records, and a web UI can break things that a single quick test misses. **The outcome:** The focused checks pass, the web tests pass, and the complete iteration gate passes before the handoff. ### Steps 1. Run `git clone https://github.com/plannotator/artifact-server.git` and `cd artifact-server`. 2. Run `pnpm install`. 3. Run `pnpm check` and `pnpm test:web`. 4. Run `pnpm verify:iteration` before the handoff. 5. Read AGENTS.md for the repository engineering rules and confirm the change follows them. ### Prompt to paste into your agent ```text In a checkout of plannotator/artifact-server, make the requested change to , then run pnpm check, pnpm test:web, and pnpm verify:iteration. Expected output: a pass or fail summary for each command and a list of any rule from AGENTS.md the change touches. Verify that all three commands exit successfully before reporting the change as ready. ``` ### Caveat The README gives the commands but not their runtime, so the time estimate covers first-run setup and the gate, not a measured run. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/plannotator-artifact-server/verify-artifact-server-changes-before-handoff/