How to Migrate a Claude Artifact to Revdoku

TL;DR: Ask Claude to package the Artifact as a complete static file set and copy it to a Revdoku bucket. If direct transfer is unavailable, use Claude’s code view or download option, upload the files manually, and test before unpublishing the original.

Claude can write the website files to a Revdoku bucket and publish them when the Revdoku tools are connected.

How can you migrate a Claude Artifact to Revdoku?

Many Claude Artifacts can be migrated because they are self-contained HTML websites, React interfaces, SVGs, documents, or other content. Anthropic’s Artifact guide says you can view the underlying code, copy content, and download files from the Artifact window.

Export a basic static Claude Artifact as HTML, CSS, JavaScript, and assets. Copying front-end files will not preserve capabilities that depend on Anthropic’s hosted AI runtime.

1. Check dependencies before you migrate the Claude Artifact

Ask Claude to identify:

• Every source and asset file.
• Whether the Artifact is plain HTML or a React build.
• Any Claude-powered feature.
• External API requests.
• Persistent storage or database use.
• Secrets or environment variables.
• Files referenced in the conversation.

Remove private prompts, customer data, credentials, and unauthorized content.

2. Connect Claude to Revdoku for the Artifact migration

From the Artifact conversation:

1. Open Revdoku’s connection instructions.
2. Connect to https://app.revdoku.com/mcp.
3. Complete Revdoku OAuth.
4. Ask Claude to verify the available Revdoku tools.

Authenticate through OAuth. Do not share passwords or API keys in chat.

3. Ask Claude to export and copy the complete Artifact

Paste this prompt:

Migrate this Claude Artifact as a static website to Revdoku.

Requirements:
1. Create a complete browser-ready file tree with index.html at the root.
2. Include all HTML, compiled CSS, JavaScript, images, SVGs, fonts,
   documents, and data files needed by the Artifact.
3. Preserve folders and relative paths.
4. If this is React or another compiled interface, create the static
   production output rather than uploading unbuilt source alone.
5. Do not include secrets, API keys, private prompts, customer data,
   environment files, or local computer paths.
6. List every source file before transfer.
7. Copy every file to a new Revdoku bucket and compare the source and
   destination file counts.
8. Report any Claude-powered AI, storage, authentication, or hosted
   runtime feature that cannot work using static files alone.
9. Publish a Revdoku preview first and check navigation, assets,
   interactions, downloads, mobile layout, and direct route reloads.
10. Stop before final publishing or unpublishing the original Artifact.

Ask Claude to explain omissions plainly. A good-looking preview that loses a key feature is not a successful migration.

4. Export the Claude Artifact with the download fallback

To host the Claude Artifact elsewhere when direct copying is unavailable:

1. Open the Artifact.
2. Use Anthropic’s documented code view or download control.
3. Save every available file.
4. Place multiple files in one folder or ZIP without flattening the structure.
5. Confirm the folder contains index.html or a finished static build.
6. Upload the folder or ZIP to Revdoku.
7. Publish a preview.

A single HTML Artifact may need only one self-contained index.html. For React, ask Claude for a deployable static build with the required assets.

Compare the finished Revdoku file tree with the Artifact export before publishing.

5. Test and choose access

Test the preview in a private window:

• Check every link and interaction.
• Reload nested routes directly.
• Confirm images, fonts, and downloads load.
• Watch for browser-console errors.
• Verify no private source or secret is exposed.
• Confirm platform-only features were removed or replaced.

Then host the Artifact on Revdoku with public, password-protected, or verified-email access. A Revdoku copy can record visitor, click, and download activity, send notifications, and accept updated files at the same URL.

Read How to password protect a Claude Artifact for access details and Claude Artifacts vs Revdoku for a compact comparison.

6. Unpublish the original only after verification

Once the replacement works:

1. Save any permitted source material.
2. Open the original Artifact’s publishing control.
3. Read Claude’s current unpublish warning carefully.
4. Unpublish the original.
5. Test its old public URL while signed out.
6. Replace links and bookmarks with the new Revdoku URL.

Public Artifacts can appear in search results. Our Google audit of public Claude Artifacts shows why client material should not rely on an obscure public address.

What does not migrate with a Claude Artifact export?

Copying files does not reproduce Claude’s hosted AI runtime, persistent storage, a platform database, secret environment variables, or service-specific authentication. Static front-end behavior can migrate to Revdoku. Platform services require replacement integrations or a different deployment architecture.

Safest order: inventory, transfer, preview, test, publish, then unpublish the old Artifact.

codex mcp add revdoku --url https://app.revdoku.com/mcp
codex mcp login revdoku

claude mcp add --transport http revdoku https://app.revdoku.com/mcp
claude mcp login revdoku