Docs — Connect Claude to ArtifactDeploy (MCP Setup Guide)

Quick start

First create a free account and confirm your email. Then connect Claude using whichever app you use — it takes about two minutes.

MCP server URL: https://mcp.artifactdeploy.com/mcp
Transport: Streamable HTTP
Authentication: OAuth 2.1 sign-in (Claude.ai, Desktop, mobile, Claude Code), or a Bearer API key starting with sk-ad

1. Claude.ai, Claude Desktop & Claude mobile

Add ArtifactDeploy as a custom connector. You sign in with your ArtifactDeploy account — there is no key to copy.

In Claude, open Settings → Connectors and choose Add custom connector.
Name it ArtifactDeploy and paste the URL https://mcp.artifactdeploy.com/mcp. Leave the advanced OAuth fields empty.
Click Add, then Connect. A window opens on artifactdeploy.com — sign in and click Allow.
In a chat, make sure ArtifactDeploy is enabled in the tools menu, then ask Claude to deploy something.

Connectors you add on claude.ai are also available in Claude Desktop and the Claude mobile apps. Custom connectors depend on your Claude plan; on Team and Enterprise workspaces an owner may need to add the connector for the organisation first.

2. Claude Code

Option A — sign in (recommended). Add the server, then authenticate from inside Claude Code:

Terminal

claude mcp add --transport http --scope user artifactdeploy https://mcp.artifactdeploy.com/mcp

Start Claude Code, run /mcp, select artifactdeploy and choose Authenticate. Your browser opens the ArtifactDeploy sign-in and consent screen.

Option B — API key. Useful on servers and CI where a browser isn't available. Create a key on Dashboard → Connections → API keys, then:

Terminal

claude mcp add --transport http --scope user artifactdeploy \
  https://mcp.artifactdeploy.com/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Either way, /mcp should show artifactdeploy as connected with three tools.

3. API keys & other MCP clients

Any MCP client that supports Streamable HTTP can connect — either through OAuth discovery (point it at https://mcp.artifactdeploy.com/mcp and it will find the sign-in flow automatically) or by sending Authorization: Bearer YOUR_API_KEY.

For clients that only launch local servers, such as older Claude Desktop setups, use the mcp-remote bridge (needs Node.js 18+). In Claude Desktop open Settings → Developer → Edit Config, add this and restart the app:

claude_desktop_config.json

{
  "mcpServers": {
    "artifactdeploy": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.artifactdeploy.com/mcp",
        "--header", "Authorization:${AUTH_HEADER}"
      ],
      "env": { "AUTH_HEADER": "Bearer YOUR_API_KEY" }
    }
  }
}

API keys are shown once when created. Treat them like passwords, and revoke any key you no longer use.

Deploying from Claude

Once connected, just ask. Mentioning “deploy” makes it explicit. Prompts that work well:

“Build me a one-page pricing calculator in HTML and deploy it.”
“Turn these notes into a 6-slide Reveal.js deck and deploy this.”
“Deploy this dashboard as “Q3 revenue” and make it private.”
“List my deployments.”
“Delete the deployment called q3-revenue-4f2a1c.”

Claude replies with the URL, for example https://q3-revenue-4f2a1c.artifactdeploy.com, and the deployment appears in your dashboard instantly. Claude asks for permission before calling a tool the first time; you can allow it for the whole chat.

MCP tools reference

`deploy_artifact`

Uploads an artifact and returns its public URL.

Parameter	Type	Description
`title`	string, required	Human-readable name (1–100 chars). Also used to build the URL slug.
`content`	string, required	The artifact source — or base64 file data for image and pptx.
`artifact_type`	enum, required	One of html, react, revealjs, md, image, svg, pptx, csv, json, code.
`is_private`	boolean, optional	Defaults to false. When true, the URL does not serve publicly.

`list_deployments`

Lists your deployments, newest first.

Parameter	Type	Description
`limit`	integer, optional	How many to return, 1–50. Defaults to 20.

`delete_deployment`

Permanently deletes a deployment and takes its URL offline.

Parameter	Type	Description
`slug`	string, required	The deployment slug, from list_deployments or the URL.

Artifact types

The artifact_type decides which viewer the URL opens in. HTML is served as-is; everything else is wrapped in a purpose-built viewer.

Type	Value	Viewer
🌐 HTML pages	`html`	Landing pages, dashboards, mini-apps
⚛️ React components	`react`	npm imports and Tailwind supported
📽️ Slide decks	`revealjs`	Presentable Reveal.js decks
📄 Markdown	`md`	Docs and reports, typeset GitHub-style
✏️ SVG	`svg`	Diagrams, charts and icons
🖼️ Images	`image`	PNG, JPEG, GIF and WebP
📊 PowerPoint	`pptx`	In-browser preview + download
📋 CSV	`csv`	Searchable, sortable data tables
🧾 JSON	`json`	Collapsible tree viewer
💻 Code	`code`	Syntax-highlighted source files

Notes on specific types

React: send a single component file and default-export the component. import from npm works — packages such as lucide-react, recharts, framer-motion and lodash load automatically from the esm.sh CDN — and Tailwind classes are styled. TypeScript is fine. Imports of local files or shadcn/ui (@/components/ui/…) only exist inside Claude's own preview; ask Claude to inline those components before deploying.
Slides: send the <section> elements of a Reveal.js deck; the theme, controls and keyboard navigation are added for you.
Images: send PNG, JPEG, GIF or WebP data as base64 (a data: URL is fine). Use svg for SVG markup.
PowerPoint: send the .pptx file as base64. The URL shows an in-browser preview (powered by Microsoft Office Online) and a Download button. In Claude Code, Claude can read and encode a local file for you — ask it to “deploy slides.pptx”.
Size: each artifact can be up to 20 MB.

URLs, prefixes & privacy

By default each deployment gets its own subdomain built from the title plus a short random suffix: https://crypto-dash-7f3a1c.artifactdeploy.com.

On Pro and Team you can claim a custom prefix in Settings. New deployments then live under it: https://yourname.artifactdeploy.com/crypto-dash-7f3a1c.

Deploy with is_private: true (or ask Claude to “make it private”) and the URL returns a “private” page instead of the content.

Plan limits

Free accounts can have 3 active deployments at a time — delete one to free a slot. Pro and Team are unlimited. See pricing for storage and other limits.

Security & revoking access

Every app you connect with sign-in appears on the Connections page under Connected apps, and any API keys you created are listed below it. Disconnecting an app or revoking a key takes effect immediately. Keys and tokens are stored only as SHA-256 hashes, and sign-in uses OAuth 2.1 with PKCE, so a leaked authorization code can't be redeemed by anyone else.

Troubleshooting

The connector says it couldn't connect or authorize

Check the URL is exactly https://mcp.artifactdeploy.com/mcp (ending in /mcp). Remove the connector and add it again to restart sign-in. Make sure you clicked Allow on the ArtifactDeploy screen and that pop-ups aren't blocked.

“Invalid or missing API key” (401)

With an API key, the header must be exactly Authorization: Bearer sk-ad…, and the key must not have been revoked. Keys created before 28 September 2026 were retired during a security upgrade — create a new one.

Claude doesn't show the tools

In Claude.ai, enable ArtifactDeploy in the chat's tools menu. In Claude Code run /mcp to see the status. In Claude Desktop with mcp-remote, check the JSON is valid, Node.js is installed and you restarted the app completely.

A React deployment shows an error box

The message says what went wrong — usually an import that only exists in Claude's preview, or a runtime error in the component. Paste the message back to Claude and ask it to fix and redeploy.

“Free plan limit … reached”

You have 3 active deployments. Ask Claude to list and delete an old one, delete it from the dashboard, or upgrade.

Still stuck?

Email [email protected] with the error message and we'll help.

Connect Claude to ArtifactDeploy