Sitejump

Knowledge

Which AI assistants can run a Sitejump migration?

The Model Context Protocol (MCP) allows an AI builder to use Sitejump tools directly within its own workflow. By connecting a single URL, the builder can audit a website and process its migration package. Because hosted web builders and local coding environments handle the final output differently, this guide clarifies what to expect from each.

Supported builders and coding workspaces

The following platforms connect directly to Sitejump. Web builders typically create a hosted project, while coding workspaces generate a codebase for you to deploy manually.

AssistantRebuild targetTypical hosting
LovableLovable projectOne-click Lovable hosting + custom domain
v0 by Vercelv0 projectVercel
Replit AgentReplit projectReplit hosting
Claude CodePortable React + Tailwind repoVercel, Netlify, Cloudflare, or GitHub Pages
CursorPortable React + Tailwind repoVercel, Netlify, or Cloudflare Pages
Codex, Cline, VS Code CopilotMigration inspectionVercel, Netlify, Cloudflare, or self-hosted
  • Lovable. The most automated path. Lovable rebuilds, hosts, and publishes the site, then connects Google Search Console for you.
  • v0 by Vercel. Integrates via a custom MCP server within the v0 prompt workflow.
  • Replit Agent. Replit Agent loads Sitejump tools directly into the project environment.
  • Claude Code. Generates a full codebase on your local machine. Prompts are optimized for a self-hosted repository.
  • Cursor. Add the connector via Settings → MCP. The migration includes instructions tailored for Cursor.
  • Codex, Cline, VS Code Copilot. Works with any coding assistant that supports MCP via Streamable HTTP with OAuth 2.1.

The destination you select during the audit remains linked to the migration. For coding workspaces, choose Claude or Cursor to ensure page prompts are written for those environments and a portable React + Tailwind repository.

Monitor the migration in real time

The connection is two-way. As the assistant works, it sends status updates to your migration page on sitejump.dev—logging completed audits, redirect maps, and page rebuilds. You don't need to watch the chat to know the status. If the assistant needs a decision, such as which pages to prioritize, it will post the question on your migration page as well as in the chat. You will also receive email notifications when pages are finished and when final go-live checks pass.

Connection steps

The process is consistent across platforms: paste the URL, sign in with Google, and you're ready. View the full details on the MCP connect page.

Custom MCP

Connect Sitejump to your assistant

  1. 1
    Paste these values into your assistant

    Use the exact name provided if your client requires a server name.

    NameSitejump
    URLhttps://sitejump.dev/mcp
    • In Lovable, click + in the chat input → Project connectors → All connectors → Custom MCP.
    • Paste the URL and name the connector Sitejump.

    Destination: Lovable can rebuild, host, and publish your site, including Google Search Console integration.

  2. 2
    Sign in and select "Always allow"

    You only need to do this once. Selecting "Always allow" prevents the assistant from stopping for confirmation at every step.

  3. 3
    Send your first message

    Start a new chat and send: Use Sitejump connector. The assistant will then run the audit and ask for your site URL.

Why ChatGPT, Gemini, and Claude Chat are not listed

ChatGPT
Custom MCP servers require Developer mode. Full read/write MCP is currently a beta feature limited to Business, Enterprise, and Edu plans. Standard Plus or Free accounts cannot yet add the Sitejump URL.
Gemini app
The Gemini web app does not support custom MCP servers. MCP is currently restricted to Google's developer tools, such as the Gemini and Antigravity CLIs.
Claude Desktop and Web
While these can connect to the Sitejump MCP server to inspect a migration, they are not designed as end-to-end web builders. Use Claude Code if you need the migration written into a codebase.

Platform support for MCP is evolving quickly. We update this list as soon as custom MCP support becomes generally available for these tools.

If your assistant doesn't support custom MCP

The connector is not a requirement for migration. You can run a free audit, purchase the migration, and download the resulting ZIP file from your account. This contains all pages, the redirect map, design tokens, and a rebuild brief that any developer or coding assistant can use.

Ask the AI assistant

← Back to the knowledge base