WPConvert MCP

What the WPConvert MCP MCP server does

The WPConvert MCP MCP server gives AI assistants an MCP interface for sending frontend project folders to WPConvert.ai and receiving WordPress theme results. It does not perform theme generation locally. The repository contains the MCP client and related developer tools; the conversion engine, parsing logic, AI prompts, quota handling, and theme generation run on WPConvert.ai servers.

The server is intended for projects that an agent can access on the local filesystem. It packages the selected folder, sends it to the hosted API over HTTPS, and tracks the resulting conversion job. The source project is not modified, and WordPress credentials are not needed.

Free verified accounts can create a limited number of preview-only developer conversions. Accounts with PRO, Agency, or PAYG access can download the generated theme.zip when the conversion succeeds.

How it works

A typical agent workflow begins with a capability check using wpconvert_quota. The agent then calls wpconvert_convert_folder, which archives the folder and starts a conversion. Because conversion is asynchronous, the agent polls with wpconvert_check_status until the job completes.

The final step depends on account capability. wpconvert_download_result retrieves theme.zip when downloading is permitted. wpconvert_create_preview creates a WordPress Playground URL for preview-only results or for users who want to inspect the output in a browser. wpconvert_explain_failure returns a failure explanation and recovery information when a job does not succeed.

The service uses the same credits as dashboard conversions. Successful paid conversions consume one credit, while failed conversions are refunded. A preview-only job cannot later become downloadable; after upgrading or adding credits, the project must be converted again.

Setup and configuration

Install and run the package through Node.js 18 or newer. An MCP host can launch the server with npx -y @wpconvert/mcp; pinning the package version, such as @wpconvert/mcp@0.3.1, provides a deterministic installation.

Set WPCONVERT_API_KEY to an API key obtained from the WPConvert dashboard under Settings → API & CLI. The key is required for API access. WPCONVERT_API_BASE is optional and can point to a non-default API host for testing.

A representative MCP configuration uses the npx command, passes the package as an argument, and supplies the API key through the server environment. The repository documents configuration examples for Cursor and Claude Desktop, as well as a broader agent workflow.

Tools and capabilities

The six MCP tools support these operations:

• Inspect quota, credits, and the recommended next action.
• Package a local folder and queue a conversion.
• Poll the status of a conversion job.
• Download the generated WordPress theme archive when authorized.
• Create a WordPress Playground preview URL.
• Explain a failed conversion and suggest recovery information.

The MCP package is a thin client for the hosted API. It does not include the conversion backend or independently implement the conversion process.

Limitations and notes

Only upload projects that you own or are authorized to process. The repository’s CLI excludes common secret files, dependency directories, version-control data, and build output by default, but the MCP material does not describe equivalent folder-filtering controls for every MCP call. Review the files being sent before starting a conversion.

Preview URLs are temporary and have single-use limitations according to the documented CLI output. Free preview access is limited to three lifetime developer conversions, and those jobs do not provide a later ZIP download. The MCP server also depends on network access to WPConvert.ai, valid account permissions, and available credits or preview entitlement.