Altered Digital Migration

Claude Connect

Hand off your migrated Sanity project to Claude Desktop via the Sanity MCP server for ongoing edits.

What is Claude Connect?

Claude Connect lets you hand your migrated Sanity project to Claude Desktop (or any MCP-compatible client) via the Sanity MCP server. Claude can then read your content, suggest edits, generate new pages, and clean up your Sanity project — all through natural language.

How it works

  1. You create a scoped Sanity API token (read/write) in Sanity Manage.
  2. The plugin stores this token separately from your migration write token (encrypted, revocable independently).
  3. The Worker generates a Claude Desktop config snippet + a deep-link that installs the MCP server with your project credentials.
  4. You paste the config into Claude Desktop (or click the deep-link) and start chatting.

Revoking the Claude connection never breaks in-flight migrations — the MCP token is stored in a separate column pair (mcp_token_enc / mcp_token_iv) from the migration write token.

Setup

  1. Go to Altered Digital → Claude Connect.
  2. In Sanity Manage → API → Tokens, create a new token with read+write permissions.
  3. Paste the token into the plugin's Claude Connect page.
  4. Copy the generated config snippet (or click the deep-link to auto-install in Claude Desktop).

Starter prompts

Once connected, try these prompts in Claude Desktop:

  • "Review my migrated blog posts and suggest SEO improvements"
  • "Generate alt text for any images missing descriptions"
  • "Create a new landing page based on my existing hero sections"
  • "Find and fix any broken internal links in my content"
  • "Summarize my site's content structure and suggest schema improvements"
  • "Write a new about page that matches my existing tone and style"
  • "Audit my content for accessibility issues (heading hierarchy, alt text, color contrast)"
  • "Generate a content calendar based on my existing post topics"

Revoking

Click Revoke on the Claude Connect page to clear the stored MCP token. The Worker sets both columns to NULL and invalidates the cache. Your migration token is unaffected.

On this page