The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Artifyde MCP listing page.
A permanent home for your agent's HTML artifacts — over MCP.
Your agent turns out real, finished work as rendered HTML: dashboards, prototypes, reports, decks. Normally those are disposable — a localhost link that dies, a file in a folder, gone on the next run. This Model Context Protocol server gives each one a permanent home on Artifyde: a stable link anyone can open, share, mark up, and version on every re-publish — without your agent leaving its MCP host.
It wraps the Artifyde API, so any MCP-capable client (Claude Desktop, Claude Code, Cursor, and others) can publish and manage artifacts directly.
The server runs over stdio and is launched with npx, so there's nothing to install globally. Add it to your MCP host's config.
If you already use the artifyde CLI, pull the token straight from its store instead of pasting it:
--scope user makes it available in every project; drop it to add for the current project only. Restart Claude Code (or run /mcp) to see the tools.
Install the one-click bundle: download artifyde-mcp.mcpb from the latest release and open it (Settings → Extensions), then paste your token in the extension's settings. Or add the JSON block below to claude_desktop_config.json.
Or in ~/.codex/config.toml (shared by the Codex CLI and IDE extension):
Any host that takes an mcpServers JSON block:
Set one credential in env:
ARTIFYDE_TOKEN — a per-user login token (vk_…). Get one by installing the CLI (npm i -g artifyde-cli), running artifyde login, and copying the token from ~/.config/artifyde/config.json. This is the recommended option: the server acts as you.ARTIFYDE_API_KEY — an admin shared-owner key (for programmatic/agent identities on self-hosted instances). A bearer token wins if both are set.Without a credential the server still starts and can read public pages; publishing and private access require one.
By default the server talks to the hosted instance at https://artifyde.com. Point it elsewhere (e.g. a self-hosted or preview instance) with ARTIFYDE_URL.
| Tool | What it does |
|---|---|
push_artifact | Publish HTML → a stable view URL. Re-push to a page_id to add a version. |
pull_artifact | Download a version's byte-exact HTML. |
get_page | Page metadata + version history. |
list_pages | Your pages, with version/comment counts (filter by archived / query). |
rename_page | Set a page's display title. |
archive_page / unarchive_page | Hide/restore a page (read-only when archived). |
get_share | A page's visibility + invited-email list. |
set_visibility | Make a page public or private. |
share_page / unshare_page | Invite / revoke an email on a private page. |
list_comments | Read a page's comment threads. |
create_comment | Post a comment (or reply) on a version. |
list_shelves / create_shelf | Manage gallery groupings. |
add_page_to_shelf / remove_page_from_shelf | Organize pages onto shelves. |
whoami | The identity the server is authenticated as. |
Every tool is annotated with readOnlyHint/destructiveHint/idempotentHint so hosts can gate confirmations appropriately.
This server is a thin client for the Artifyde API: the only data it transmits is what you ask it to (the HTML you publish, page ids, comment text, share emails), sent over HTTPS to the Artifyde server you configure (https://artifyde.com by default). Your token is read from the environment (or the Claude Desktop extension's config) and used solely to authenticate those API calls; nothing is logged or sent anywhere else. See the Artifyde privacy policy for how the hosted service handles your data.
The Artifyde API client under src/core/ is vendored from the (private) Artifyde monorepo's @artifyde/core package; the API surface it wraps is the server's stable /v1 contract.
See PUBLISHING.md for the release + marketplace-listing runbook.
Issues and questions: github.com/kennethkoontz/artifyde-mcp/issues