Artifacts MCP Server

Self-hosted artifact publishing: POST HTML/JSX/Markdown/zip, get an unguessable URL on your domain

What you get

Self-hosted, Claude-style artifact publishing

AI assistants produce a lot of shareable output: dashboards, prototypes, reports, small apps. Claude's hosted artifacts work well, but the URLs live on someone else's infrastructure. This is the self-hosted version, about 1,100 lines. You POST content, it serves the rendered result at an unguessable URL on a domain you control.

• Four content types. — HTML, JSX/TSX (a single React component, no build step), Markdown, and zipped static sites
• Agent-native, human-friendly. — A built-in MCP server lets Claude Code, Codex, or any MCP client publish with one tool call. Humans get a drag-and-drop web UI at / (behind an admin login) and a CLI
• Two-tier auth. — An admin logs into the dashboard with a password; CLI and MCP carry scoped, revocable API keys (read / publish / full) with optional expiry, so you never share one master secret
• Optional viewer frame. — A slim top toolbar (title, copy link, hide) like Claude, Gemini, and ChatGPT artifacts. Toggle it globally in Settings or per artifact; ?raw=1 always serves the bare content
• Organize by project. — Group artifacts built for the same project into collapsible sections, with a search box across project, title, slug, and tags. Tags stay for cross-cutting labels
• Lifecycle controls. — Custom slugs, rename, tags, disable without deleting, auto-expire, delete

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.