KodExport MCP · public beta

Bring your app.
Let your agent
take it from here.

Give your coding agent the data, source evidence and export tools to start moving Bubble, Framer, Webflow and WordPress projects into code you own.

Hosted on CloudflareMIT licensedNo local server needed
One connection. Four platforms.

Add KodExport to your agent.

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.

Bubble → Cloudflare / AWS

Your data, with a path forward.

Read exposed API schemas and records. Supply application JSON, workflow notes and screenshots so your agent can reconstruct the behavior behind each screen.

  • Preserve record IDs and raw data.
  • Generate Workers + D1 or Lambda + DynamoDB starters.
  • Track missing privacy rules, UI and workflows explicitly.

Workflow endpoints start as placeholders. Your agent still needs to implement and test your application logic.

Framer → Astro / React

Your content, ready to rebuild.

Read owner CMS collections, page metadata and custom source. Generate an Astro project with React content templates and editable local JSON.

  • Bring over CMS records and preserve custom code as evidence.
  • Optionally capture up to three published pages and assets.
  • Download a project with a clear migration report.

Public pages remain HTML snapshots. Original design, animations and custom components need a reviewed rebuild.

Webflow → Astro / React

Your CMS, ready for a new home.

Read the configured site, collection schemas and published items through Webflow’s Data API. Preserve IDs, field values and content references.

  • Select collections and inspect pagination.
  • Generate an editable Astro and React content project.
  • Keep raw source evidence and a list of content gaps.

Design templates, interactions, forms, localization and hosted application services need reconstruction.

WordPress → Astro / React

Your published content, in your project.

Read posts, pages and standard REST-exposed post types. Public content needs only your site URL; owner access can use an application password.

  • Preserve record IDs, raw fields and media references.
  • Exclude password-protected content from generated pages.
  • Choose serverless hosting or a Node server.

Themes, plugin PHP, users/passwords and application logic need a separate rebuild. Media files may still point to the source host.

Choose where you’re moving

Your platform. Your cloud. Your runtime.

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.

From connection to source

Keep the agent grounded
in your actual app.

  1. Add the server.

    Use an install button or paste the server URL into your client’s remote MCP settings.

  2. Choose your source access.

    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.

  3. Follow your migration plan.

    Your agent guides inspection, export, reconstruction, local validation, deployment preparation, staging and cutover. It records evidence and keeps a rollback checkpoint.

Try this with your agent

Start with your selected stack.

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.

Manual client configuration

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"
    }
  }
}
What happens to my data?

Each authorization creates a separate workspace. Source credentials are encrypted in its OAuth grant and are not returned by tools. Source files 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.

What is included in this beta?

Owner data reads, evidence storage, project generation and downloadable ZIPs. 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. Export requests are limited to six per minute per connection.

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.

Can I run it locally?

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.2.0.tgz

Need the whole migration handled?

We can help rebuild authentication, workflows, integrations and the rest of your app.

Explore guided migration