straight from claudeMCP

Made it in Claude? Ship it from Claude.

Connect Artifacky to Claude once — then just say “publish this to my Artifacky.” It goes live with a real URL without leaving the chat. No export, no upload, no copy-paste.

What it does

Artifacky runs a Model Context Protocol server. Any MCP-capable agent (Claude Code, Claude Desktop, the claude.ai connector, and others) can call these tools:

  • upload_artifactPublish a self-contained HTML document as an artifact on the user's Artifacky page; returns the public URL.
  • list_my_artifactsList the artifacts the authenticated user has published on Artifacky.
  • delete_artifactDelete one of the authenticated user's artifacts by its slug.

Endpoint: https://mcp.artifacky.com/mcp

Claude Code / Claude Desktop (token)

Generate a personal access token in Artifacky → Settings, then add the server to your MCP config:

{
  "mcpServers": {
    "artifacky": {
      "type": "http",
      "url": "https://mcp.artifacky.com/mcp",
      "headers": { "Authorization": "Bearer ak_your_token_here" }
    }
  }
}

Then, in any chat: “Publish this HTML to my Artifacky.”

claude.ai / custom connector (OAuth)

  1. In Claude, go to Settings → Connectors → Add custom connector.
  2. Enter the URL https://mcp.artifacky.com/mcp and click Connect.
  3. A browser opens — sign in to Artifacky and click Allow on the consent screen.
  4. Done. In any chat: “publish this HTML to my Artifacky.”

Good to know

  • ✦Tokens are revocable — name and revoke them anytime in Settings.
  • ✦Finish onboarding (pick a handle) before publishing.
  • ✦Enforced server-side: 5 MB HTML cap, the free-tier artifact limit, per-user slug uniqueness.

More: /about · /facts · /pricing