Artifacts
MCP server that turns agent-generated Markdown, HTML, and text into persistent links, with tools to create, update, remove, list, and retrieve artifacts.
README
Artifacts
Artifacts turns agent-generated Markdown, HTML, and text into persistent links. It exposes a streamable HTTP MCP server for creating and managing documents, plus a small server-rendered web interface for reading and finding them.
[!WARNING] Artifacts is unversioned pre-alpha software. It has no compatibility guarantees: configuration, storage, MCP tools, and URLs may change or be removed without a migration path.
Artifacts has no authentication or authorization. Run it only on a trusted internal network or loopback interface, and put an authentication-capable proxy in front of it before granting broader network access. Do not expose it directly to the public internet.
Prerequisites
- Docker with a running Docker daemon for the recommended quickstart.
- Node.js 24 or newer and pnpm 11 for local development.
Docker quickstart
From the repository root:
corepack enable
pnpm install --frozen-lockfile
pnpm docker:check
pnpm docker:start
Wait until docker ps reports the artifacts container as healthy, then open
http://localhost:4242. The MCP endpoint is http://localhost:4242/mcp.
pnpm docker:logs
pnpm docker:stop
The helper builds locally, binds only to 127.0.0.1, and uses the deterministic container name
artifacts. If an ignored docker-compose.yaml exists, the same commands delegate to Docker
Compose so operators can maintain a private topology without committing it.
Connect an agent
Replace http://localhost:4242 in these examples with the URL that your trusted network or proxy
uses to reach the deployment.
Codex:
codex mcp add artifacts --url http://localhost:4242/mcp
Claude Code:
claude mcp add --transport http --scope user artifacts http://localhost:4242/mcp
The server exposes add_artifact, update_artifact, remove_artifact, list_artifacts, and
get_artifact.
Optional artifact skill
The bundled skill teaches an agent when to create or update a document and includes templates. From the repository root, install it for the client you use:
Codex:
mkdir -p ~/.agents/skills
ln -s "$PWD/skills/artifact" ~/.agents/skills/artifact
Claude Code:
mkdir -p ~/.claude/skills
ln -s "$PWD/skills/artifact" ~/.claude/skills/artifact
Restart the client after installing the skill. The skill is optional; MCP tools work without it.
Configuration and persistence
The zero-configuration Docker path needs no .env file. Copy .env.example to .env only to
override Docker defaults.
| Variable | Default | Purpose |
|---|---|---|
ARTIFACTS_PORT |
4242 |
Loopback host and container port used by the Docker helper. |
ARTIFACTS_PUBLIC_BASE_URL |
http://localhost:4242 |
Base URL returned for artifacts; must be an absolute HTTP(S) URL without credentials, query, or fragment. |
ARTIFACTS_FILES_MOUNT |
artifacts-files |
Docker volume name or existing absolute host directory for document bodies. |
ARTIFACTS_DATABASE_MOUNT |
artifacts-database |
Separate Docker volume name or existing absolute host directory for SQLite. |
Named volumes survive container replacement and pnpm docker:stop. The files and database mounts
must be different. Absolute bind-mount directories must exist and be writable from the container by
the non-root node user (uid 1000); pnpm docker:start probes both before replacing an existing
container.
For a consistent backup, stop the service and treat the SQLite database and stored files as one
backup set. With the default named volumes, export both into a newly created backups directory:
pnpm docker:stop
mkdir -p backups
docker run --rm --mount source=artifacts-files,target=/source,readonly --mount "type=bind,source=$PWD/backups,target=/backup" alpine tar -czf /backup/artifacts-files.tgz -C /source .
docker run --rm --mount source=artifacts-database,target=/source,readonly --mount "type=bind,source=$PWD/backups,target=/backup" alpine tar -czf /backup/artifacts-database.tgz -C /source .
For bind mounts, copy the two configured directories while the service is stopped. Restore both sources from the same backup before restarting.
Direct development uses .env.development and intentionally separate paths:
| Variable | Default |
|---|---|
ARTIFACTS_PORT |
3000 |
ARTIFACTS_PUBLIC_BASE_URL |
http://localhost:3000 |
ARTIFACTS_FILES_DIR |
data/development/files |
ARTIFACTS_DATABASE_PATH |
data/development/database/artifacts.db |
See .env.development.example for copyable overrides. Docker mount variables and direct-runtime
path variables are deliberately different; one is not an alias for the other.
Development
corepack enable
pnpm install --frozen-lockfile
pnpm dev
Before opening a pull request:
pnpm fmt
pnpm lint
pnpm test
pnpm build
pnpm start runs an existing build with development storage defaults. See
CONTRIBUTING.md for the contribution workflow.
Troubleshooting
Docker CLI not found: install Docker Desktop or Docker Engine, then rerunpnpm docker:check.Docker daemon is unavailable: start Docker Desktop or the Docker service.Docker Compose v2 is unavailable: install the Compose plugin or remove/rename the localdocker-compose.yamlto use the bare-Docker path.- A mount error before startup: use different valid volume names, or create the absolute files and database directories first. Commas are not supported in mount sources.
- Returned links point at the wrong host: set
ARTIFACTS_PUBLIC_BASE_URLto the externally reachable base URL and restart. - Port 4242 is occupied: set
ARTIFACTS_PORTand the matchingARTIFACTS_PUBLIC_BASE_URLin.env.
Architecture
Artifacts is a Node.js 24 TypeScript application built on Hono. The same process serves the web UI,
artifact routes, static assets, and the streamable HTTP MCP endpoint at /mcp. Metadata lives in
SQLite while document bodies live in a separate files directory. Markdown is rendered on the server
with syntax highlighting; Mermaid diagrams are rendered in the browser. The Docker image is a
two-stage Alpine build that runs as the non-root node user and writes only to its two persistence
mounts.
Security and license
Read SECURITY.md before deploying. Artifacts is available under the MIT License.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.