Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
A home for your agent's HTML artifacts - publish, pull, share and review them over MCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
ARTIFYDE_TOKEN, ARTIFYDE_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp"
],
"env": {
"ARTIFYDE_TOKEN": "your-value",
"ARTIFYDE_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add artifyde --env ARTIFYDE_TOKEN=your-value --env ARTIFYDE_URL=your-value -- npx -y artifyde-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"artifyde": {
"command": "npx",
"args": [
"-y",
"artifyde-mcp"
],
"env": {
"ARTIFYDE_TOKEN": "your-value",
"ARTIFYDE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"artifyde": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"artifyde-mcp"
],
"env": {
"ARTIFYDE_TOKEN": "your-value",
"ARTIFYDE_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ARTIFYDE_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain artifyde.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ARTIFYDE_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.2) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
claude mcp add artifyde --scope user -e ARTIFYDE_TOKEN=vk_your_login_token -- npx -y artifyde-mcp
If you already use the artifyde CLI, pull the token straight from its store instead of pasting it:
claude mcp add artifyde --scope user \
-e ARTIFYDE_TOKEN="$(jq -r '.servers["https://artifyde.com"].token' ~/.config/artifyde/config.json)" \ -- npx -y artifyde-mcp
--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.
codex mcp add artifyde --env ARTIFYDE_TOKEN=vk_your_login_token -- npx -y artifyde-mcp
Or in ~/.codex/config.toml (shared by the Codex CLI and IDE extension):
[mcp_servers.artifyde]
command = "npx" args = ["-y", "artifyde-mcp"]
[mcp_servers.artifyde.env] ARTIFYDE_TOKEN = "vk_your_login_token"
Any host that takes an mcpServers JSON block:
{
"mcpServers": { "artifyde": { "command": "npx", "args": ["-y", "artifyde-mcp"], "env": { "ARTIFYDE_TOKEN": "vk_your_login_token" } } } }
Set one credential in env:
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.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.
bun install
bun test # unit tests (Bun's built-in runner) bun run typecheck # tsc --noEmit bun run start # run from source over stdio bun run bundle # build the Claude Desktop .mcpb bundle
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