Artifacts MCP Server

Artifacts MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. 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

What the assistant can call

Once Artifacts is connected, these are the calls the assistant has available:

• 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
• Two — tier auth.** An admin logs into the dashboard with a password; CLI and MCP carry scoped, revocable API keys (read / publish / full)
• Abuse — resistant.** Login and unlock endpoints are rate-limited per client IP (failures only), and password hashing runs off the event loop, so a burst of

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: ARTIFACTS_API_KEY, BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Artifacts's toolset — Agent, Two, Abuse — is a fair guide to whether it matches your workflow. It is maintained by kuyazee; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the artifacts mcp server does with a few real requests.