Connect the MCP

The Model Context Protocol (MCP) is the bridge between Claude and the Convertex editor. It allows Claude to push generated code into your projects, manage your pages, and launch conversions — directly from the conversation.

The MCP handles the interaction with the editor (projects, pages, conversion). The HTML/CSS generation rules are provided by the skills, which must be installed beforehand.

Prerequisite: generate your API key

Before configuring the MCP, you need to generate an API key in your Convertex account:

Go to convertex.ai and sign in to your account.

Generate an API key

Click the Skills & MCP button in the toolbar, then open the MCP tab. Click Generate a key.

Copy the key

Your key starts with cvx_. Copy it immediately — it will not be shown again after this step.

Keep your API key safe. If you lose it, you will need to generate a new one. You can have up to 3 active keys per account.

Install the MCP

.mcpb extension (recommended)

Claude Desktop supports one-click installation via a .mcpb extension file. No Node.js installation required.

Download the file

In the MCP tab of Convertex, click Install for Claude Desktop to download the convertex.mcpb file.

Install the extension

Double-click the downloaded file. Claude Desktop opens and asks you to confirm the installation.

Enter your API key

Claude Desktop asks for your API key — paste the one you generated above (cvx_...).

That's it. The MCP is active immediately.

Manual configuration (JSON)

If you prefer to configure manually, open Settings > Developer > Edit Config in Claude Desktop and paste:

{
  "mcpServers": {
    "convertex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.convertex.ai/mcp",
        "--header",
        "Authorization: Bearer cvx_YOUR_KEY_HERE"
      ]
    }
  }
}

Replace cvx_YOUR_KEY_HERE with your API key. Save and fully restart Claude Desktop.

Requires Node.js installed on your machine.

Manual configuration for Cursor, VS Code, or Claude Code

You can also configure the MCP manually via JSON:

{
  "mcpServers": {
    "convertex": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.convertex.ai/mcp",
        "--header",
        "Authorization: Bearer cvx_YOUR_KEY_HERE"
      ]
    }
  }
}

Cursor — Settings > MCP > Add new MCP server and paste the JSON block.

Claude Code — Two possible locations:

Global (~/.claude/settings.json) — applies to all your projects.
Per project (.mcp.json at the project root) — applies only to this project.

Requires Node.js installed on your machine. To share the config with your team, use .mcp.json and commit it to your repo. To keep the key private, add .mcp.json to .gitignore or use the global config.

Verify the connection

After configuration, start a new conversation and ask:

"Test the Convertex connection"

Claude should call the whoami tool and return your account information (plan, remaining conversions, etc.).

Available tools

Once the MCP is connected, Claude has access to the following tools to interact with the Convertex editor. You don't need to call them yourself — Claude uses them automatically.

Project and page management

Tool	Role	When Claude uses it
`whoami`	Checks the connection and account info	When you ask to test the connection
`list_projects` / `create_project`	List or create projects	When you work on a new project
`rename_project` / `delete_project`	Rename or delete a project	On explicit request
`list_pages` / `get_page`	List or read pages of a project	To view existing content
`create_page`	Create a new page with the generated code	After generation, to push the result to Convertex
`update_page`	Replace the entire content of a page	For major modifications
`patch_page`	Apply targeted modifications (find & replace)	For small adjustments (faster than `update_page`)
`delete_page`	Delete a page	On explicit request
`notify_sync_start`	Notify the interface before a modification	Automatically before each create/update/delete

Building large pages (4+ sections)

Tool	Role	When Claude uses it
`add_section`	Add a section to a page being built	For pages with many sections
`assemble_page`	Assemble all sections into a complete page	After all sections have been added

Styles and conversion

Tool	Role	When Claude uses it
`get_project_styles`	Retrieves CSS classes used in the project	Before creating a new page, to reuse existing classes
`get_reference_styles`	Retrieves uploaded Webflow reference styles	When reference styles are configured
`convert`	Converts HTML/CSS to Webflow-compatible format	When you request a conversion
`get_history`	Views conversion history	On explicit request
`validate_output`	Checks generated code against the rules	On explicit request (e.g., "validate the code")

The typical workflow

In practice, when you ask "With Convertex, create a hero", here is what happens:

The skills (already loaded) provide the generation rules to Claude.
Claude asks you the 3 questions (Client-First? rem/px? language?).
Claude generates the code HTML/CSS following the skill rules.
create_page() — the MCP pushes the result to the Convertex editor.

For modifications:

Small adjustment -> patch_page()
Major overhaul -> update_page()

Troubleshooting

Convertex tools don't appear

Check your API key. It must start with cvx_ and be active in your account.
Check the JSON syntax. Validate at jsonlint.com.
Fully restart. Close the application and reopen it.

Authentication error

Your API key may have been revoked. Check in your Convertex account settings and generate a new one if needed.

Claude generates code but doesn't push it to Convertex

Verify that the MCP is connected (ask "Test the Convertex connection").
Add "and push the result to Convertex" to your prompt.

The MCP server requires no maintenance. Updates are deployed server-side — your local configuration remains unchanged.

Next step

The MCP is connected. Install the Chrome extension to capture sections from existing websites, or go directly to the first test.

On this page