Artifact Server MCP
A self-hosted artifact server with MCP: an agent publishes HTML, mockups and reports while a team reviews versions and comments
- 268 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The MCP tools publish and delete artifacts and change their visibility and tags, and review links open materials to other people
- The server stores files and metadata, and team mode needs a domain, storage and an identity provider setup
Install
- Works in
Manual install
git clone https://github.com/plannotator/artifact-server.gitLocal run: `cd artifact-server`, `pnpm install`, `pnpm dev`. Needs Node.js 24.12 and pnpm 10.34.3. Then `artifactserver connect` and `npx skills add plannotator/artifact-server`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The MCP tools publish and delete artifacts and change their visibility and tags, and review links open materials to other people
- The server stores files and metadata, and team mode needs a domain, storage and an identity provider setup
This is third-party code. Review the repository files before installing.
What it does
Artifact Server keeps the results of an agent's work in one place: HTML documents, images, video, plans and prototypes. Artifacts are organised by project and get versions, review links and comments on a specific version. The project positions itself as an open, self-hostable alternative to Claude Code artifacts. The server has a built-in MCP endpoint `POST /mcp` with the same operations and permissions as the CLI and HTTP API. The tools are split into groups: capability discovery, projects, reading and diffing versions, publication through file upload, visibility and tag management, and comments. An agent first calls `artifact_capabilities`, then `artifact_create_upload` and `artifact_commit_upload`. The result carries a full-screen review link that the agent hands over first. The `artifactserver connect` command connects a local client: Codex, Claude Code, Cursor or VS Code. For a team server you give the client the `/mcp` address and sign in through the identity provider. A portable Skill installs with `npx skills add plannotator/artifact-server`. Locally the server keeps metadata in SQLite, and for a team it deploys on Cloudflare, Compose, Kubernetes, AWS or Google Cloud.
Who it is for. Teams whose agents produce HTML mockups, reports and prototypes and who need to collect them in one place with versions and discussion.
Good fit when
- An agent built an HTML plan document and it must reach colleagues as a link for viewing and comments
- You need to compare two versions of a mockup and go back to the previous one if the new one is worse
- Working artifacts must not live in an outside cloud and the server has to run on your side
- Reviewers want to comment on an exact version and the agent has to read those comments through MCP
Not a fit when
- You only need to link to a file in a repository: Git is enough, and the server adds storage and viewing
- You cannot run Node.js 24.12 and pnpm: the source requires those versions
- You need publishing to a public website: the server is for team viewing and discussion
- You need ready hosting without administration: in team mode you set up a domain and storage yourself
Example request
Upload this HTML plan document to Artifact Server and send me the full-screen review link with commentsMCP
- Transport
- stdio, http
- Authentication
- OAuth
Limitations
- Running from source needs Node.js 24.12 or newer and pnpm 10.34.3. A portable Node.js package is also in the releases.
- A remote deployment needs one trusted application domain and a separate wildcard domain for content.
- Live message delivery is supported for Pi and Claude Code Channels from source, and Claude Channels are a research preview.
- The OpenCode adapter is not release-qualified.
- Git history on Cloudflare Artifacts is off by default and needs closed beta access.
How to disable. Run `artifactserver disconnect codex` (or another client) and delete the Skill from the agent's skills directory. Stop the local server, since the data sits in SQLite and a files directory. Tear down a team server following the guide of your platform.
FAQ
How do I connect Artifact Server to Codex or Claude Code?
Start the server and run `artifactserver connect`. If several clients are installed, name one: `artifactserver connect codex`, `claude`, `cursor` or `vscode`. Check it with `artifactserver doctor`.
Which MCP tools are available?
Groups: `artifact_capabilities`, projects, artifact lists and versions, publication (`artifact_create_upload`, `artifact_commit_upload`), visibility and tags, and comments. Files go through a separate upload API and MCP carries metadata.
How do I connect to a team server?
Add the `https://<your-domain>/mcp` address to the client. The client opens your identity provider and, after sign-in, the token is valid for that MCP resource only.
Where is the data stored?
Locally metadata is in SQLite and files are on disk. A team deployment uses D1 and R2 on Cloudflare or PostgreSQL and S3-compatible storage in Compose, Kubernetes, AWS and Google Cloud.
Is it safe to open someone else's artifacts?
Content is served from isolated version hosts separate from the trusted application origin used for sign-in, review and comments. Private content opens through version-scoped sessions.
Discussion
No questions or reviews yet.
Related
MCP serversThe MCP endpoint of a Salt workspace on your server: an agent creates pages, databases and comments with a person rights.
A self-hosted issue tracker and wiki on Cloudflare with MCP: 126 tools, issue leases and file claims for several agents
AFFiNE MCP Server: AFFiNE notes and databases for agents
AFFiNE MCP Server
An MCP server for AFFiNE: the agent searches, creates and edits documents, databases and comments in cloud or self-hosted AFFiNE
The official Kibela MCP server searches, reads and edits notes, folders and comments of your wiki straight from an assistant chat
A team wiki living in Git with a 51-tool MCP server: agents read and edit pages, tables and boards.
MCP server for the knowledge base Beever Atlas builds from Slack, Discord, Teams and Mattermost chats: cited answers, channel wikis, a graph
README in short
The README describes a self-hosted artifact server: why it exists, how agents and teams work with it and why it pairs with MCP and a Skill. It then covers Cloudflare, team deployment, running on a laptop, using the CLI, the security model and development records. The licence is dual: MIT or Apache 2.0.