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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。