Figma's own MCP server gives your AI assistant design context. It does not build WordPress pages. ready→made MCP is the missing step: finished, native builder layouts from the same frame.
MCP is included in Pro and Lifetime (€250 once), together with the Figma plugin. · Already a customer? Create your MCP key →
The design is finished. Now it needs to be in Elementor.
So you ask your assistant. Here, Claude Code, with the ready→made MCP server connected.
It doesn't let a model guess the layout. Our engine computes it from the frame's real geometry.
You get Elementor JSON back, and a note on which fonts the site needs.
In Elementor, right-click. Paste from other site. The images go straight into your media library.
Native containers and widgets. Same design in, same layout out. Every time.
Gutenberg, Oxygen, Etch and HTML work the same way.
The ready→made MCP server. Included in ready→made Pro.
Setup at wpconverters.com/mcp
With Figma's MCP server, an assistant like Claude or Cursor can read your frames: names, sizes, styles, variables. That is a big step. But turning that context into a WordPress page is still left to the model, and the model writes the layout from scratch each time.
If your target is a page builder, you want builder-native output, not hand-written HTML that someone has to rebuild. That is what ready→made MCP adds: it converts the frame into the builder's own format with a deterministic engine, so your assistant can paste, import and refine instead of reinventing the layout.
Add the ready→made MCP server to Claude, Cursor or Windsurf with your MCP key and your Figma access token. Copy-paste configs →
Name the frame and the builder. The assistant calls the converter as a tool.
You get native builder markup to paste or import. The assistant handles content and the last 10%.
| Figma MCP | ready→made MCP | |
|---|---|---|
| What your assistant gets | Design context: structure, styles, variables | A finished layout in your builder's format |
| Who writes the layout | The language model | A deterministic layout engine |
| Same input, same output | No, varies per run | Yes |
| WordPress builders | None natively | Elementor, Gutenberg, Oxygen, Etch, HTML |
| Best for | Coding apps from a design | Building WordPress pages from a design |
| Use them together? | Yes: context for the code around the layout | Yes: the layout itself |
The six output formats, each with a note on how to paste or import it. Free.
Outline of a Figma file or frame with layer counts and section candidates, so the assistant picks the right node. Free.
Converts one frame into Elementor (paste JSON or template), Gutenberg, Oxygen 6, Oxygen Classic, Etch or HTML and tells the assistant how to paste it.
Nothing extra. MCP access is included in ready→made Pro (€19/month) and Lifetime (€250), the same plans as the Figma plugin.
Any client that speaks the Model Context Protocol over HTTP: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code and others. Copy-paste configs for each are on the setup page.
A ready→made plan, an MCP key from your account page, and a Figma personal access token so the server can read the frame you point it at.
No. Your client sends it with each request; we forward it to Figma for that call and never store or log it.
One section at a time works best. The limit is 4,000 layers and 6 MB of output per call; the assistant can list a file's sections first and convert them one by one.
Yes. Same engine, same transformer chain, same targets. The plugin runs it inside Figma; the MCP server runs it for your assistant.
Get Pro, create your MCP key and connect Claude, Cursor or Windsurf in about two minutes.