Give your coding agent the data, source evidence and export tools to start moving Bubble, Framer, Webflow, WordPress and Wix projects into code you own.
Use a client that supports remote MCP with OAuth. Connect once, choose your stack, and follow a saved plan from source inspection to cutover.
Your client opens a consent page. Add owner credentials there if you need private data. Public Framer snapshots work without a platform key.
Read exposed API schemas and records. Supply application JSON, workflow notes and screenshots so your agent can reconstruct the behavior behind each screen.
Workflow endpoints start as placeholders. Your agent still needs to implement and test your application logic.
Read owner CMS collections, page metadata and custom source. Generate an Astro project with React content templates and editable local JSON.
Public pages remain HTML snapshots. Original design, animations and custom components need a reviewed rebuild.
Read the configured site, collection schemas and published items through Webflow’s Data API. Preserve IDs, field values and content references.
Design templates, interactions, forms, localization and hosted application services need reconstruction.
Read posts, pages and standard REST-exposed post types. Public content needs only your site URL; owner access can use an application password.
Themes, plugin PHP, users/passwords and application logic need a separate rebuild. Media files may still point to the source host.
Wix has no read-only content API, so the MCP captures what visitors see. Give your agent the site URL and it exports the published pages and assets into an Astro project.
Wix Stores, Bookings, Members, forms and Velo backend code are not recovered. Export CMS data from your Wix dashboard and give it to your agent as evidence.
The public_site_export tool needs no credentials. It works for Wix, WordPress, Framer, Webflow, Squarespace and others, and detects which one it found.
This is a front-end snapshot. JavaScript is not rendered and server-side features need a rebuild.
The security_audit_site tool audits a public site you are authorized to assess, without logging in, submitting anything or running scripts. It separates confirmed findings from items you need to check, and from hardening notes.
This is a passive check, not a penetration test. Exports include baseline security headers you can adapt.
Your agent asks for these choices and keeps them in a saved migration plan.
Cloudflare Pages for static content, Workers for APIs, and D1/R2 for durable data.
Use an install button or paste the server URL into your client’s remote MCP settings.
Approve a fresh workspace and optionally connect your source. Then choose Cloudflare or AWS and serverless or a Node server. Credentials go through the consent page, not the conversation.
Your agent guides inspection, export, reconstruction, local validation, deployment preparation, staging and cutover. It records evidence and keeps a rollback checkpoint.
Guide my Bubble migration from source inspection through deployment and cutover. Use Cloudflare with serverless functions and hosting. Create a saved migration plan, keep the generated project on this stack, and verify each stage before continuing.
Your agent can inspect public HTML and save measured reports alongside your migration checkpoints.
Check up to five pages for titles, descriptions, headings, canonical links, forms and external dependencies.
Check source and staging page pairs for missing text, changed SEO metadata, altered form counts and links or resources still on the old host.
Reports include timestamps, content hashes and findings. These checks read HTML without running JavaScript; browser, login, workflow and data tests are still required.
For clients using an mcpServers configuration. VS Code uses its own servers format; the install button handles that.
{
"mcpServers": {
"kodexport": {
"url": "https://mcp.kodexport.com/mcp"
}
}
}Each authorization creates a separate workspace. Source credentials are encrypted in its OAuth grant and are not returned by tools. Source files, audit reports and ZIPs become inaccessible after 72 hours and are removed by scheduled cleanup. Saved plans and progress notes expire after 30 days. Download links expire after one hour; anyone holding a link can download that file before it expires.
Reconnect to change credentials. Your client can revoke its connection; you can also revoke the original key in Bubble or Framer. Reconnecting starts a new workspace rather than restoring the previous one. Only connect sources you own or have permission to migrate.
Owner data reads, evidence storage, project generation, downloadable ZIPs and measured public HTML audits/comparisons. Hosted Bubble exports include up to five data types and 100 records per type. Webflow and WordPress exports include up to five selected collections/post types and 100 items each. Source reads support pagination. Framer snapshots include up to three public pages. Exports and audits share a limit of six requests per minute per connection. Audits inspect up to five public HTML pages; comparisons accept up to three explicit route pairs.
This is an agent-assisted migration toolkit. It does not automatically recreate an entire application, deploy cloud infrastructure or provide an editorial CMS dashboard. Inspect migration.json and validate the generated project before changing hosting.
The MIT-licensed local server supports stdio clients and local evidence files. Download the local package and install it with npm. npm and directory listings are separate from this hosted beta.
npm install --global https://kodexport.com/downloads/kodexport-mcp-0.4.0.tgzWe can help rebuild authentication, workflows, integrations and the rest of your app.
Explore guided migration