Question 1

Can I use WPConvert from Cursor or Claude?

Accepted Answer

Yes. WPConvert ships an MCP server (@wpconvert/mcp) that plugs into Cursor, Claude Desktop, and other MCP-compatible tools. Once it's connected, you just ask in plain English (e.g. "convert this folder into a WordPress theme") and the assistant zips, converts, and downloads the theme for you.

Question 2

Can AI agents use WPConvert?

Accepted Answer

Yes. WPConvert's CLI, API, and MCP server let AI assistants and MCP-compatible agents submit conversions, check status, and download completed WordPress themes. Browser-based AI builders still need to export or provide a local project folder unless they support this workflow directly.

Question 3

Do API, CLI, and MCP conversions use credits?

Accepted Answer

Yes — they use the exact same credit system as the dashboard. Each successful conversion uses 1 credit (Agency is unlimited), and failed conversions are refunded. There's no separate metering or surprise pricing.

Question 4

What happens if I run out of credits?

Accepted Answer

New conversions are blocked until you add credits or your plan renews — nothing is silently charged. Status checks and downloads for previous jobs keep working even with zero credits.

Question 5

Who can access developer tools?

Accepted Answer

Anyone on a Pro or Agency plan, or anyone with available pay-as-you-go credits. You create an API key in your dashboard under API & CLI, then use it from the CLI or MCP server.

Question 6

Is my code safe?

Accepted Answer

The CLI only packages your site files and automatically excludes node_modules, build caches, .git, OS junk, and secrets like .env, *.pem, *.key, .npmrc and .ssh/. Your .gitignore is honored and symlinks are never followed. You can always run with --dry-run first to see exactly what would be uploaded before anything leaves your machine.

Question 7

Should I run the CLI from my project root or build folder?

Accepted Answer

Just run it from your project folder. For plain HTML sites (most AI exports, Framer/Webflow) point it at the folder with index.html. For React/Vite/Next/Astro apps, run your build first (npm run build) and the CLI auto-detects the dist/ or build/ output. If you're unsure, run with --dry-run and it will detect the folder or tell you to build first.

Question 8

Can PAYG users use the CLI/API?

Accepted Answer

Yes. Pay-as-you-go credits include the same Pro-level conversion features as dashboard conversions, including CLI, API, and MCP access. Create an API key in your dashboard and use it from the CLI or your AI assistant.

Question 9

Can I use WPConvert in CI or agency automation?

Accepted Answer

Yes. Authenticate with your API key and call the HTTP API (or the CLI in a script) to submit conversions, poll status, and download themes from CI pipelines, internal dashboards, or client-onboarding flows.

Question 10

Does MCP work in every AI builder?

Accepted Answer

MCP works with MCP-compatible tools such as Cursor and Claude Desktop. Other MCP-compatible editors may also work depending on their MCP support. Browser-based builders like Lovable, v0, Replit, and Google AI Studio do not run WPConvert's MCP server directly. For those, export or download the project and convert the local folder with the CLI, your editor, or the dashboard.

Question 11

Which export formats are supported via the CLI?

Accepted Answer

The CLI and MCP currently produce standard WordPress themes (.zip) — the same high-fidelity output as the web app. Elementor and Gutenberg exports are coming soon and will be available once released.

Ask your AI assistant to ship WordPress