Now in beta
Coding agents for WordPress page builders
SleekAI mirrors the active page into structured files: builder data, CSS, responsive settings, and validation context. Claude Code searches and edits the page like a small project, and SleekAI applies the validated result back through the builder so the agent never has to guess from visual context alone.
♾️ Lifetime License available
Bricks
Bricks structure, content, CSS, and selected elements as files.
Elementor
Elementor containers, widgets, responsive controls, and save flow.
Breakdance
Breakdance element data, design settings, CSS, and validation.
Beaver Builder
Beaver Builder rows, columns, modules, CSS, and save steps.
Local setup
Start the local agent bridge
Claude Code runs on your machine, while SleekAI runs inside WordPress. The local @sleekwp/agent bridge connects the browser terminal to Claude Code, creates the temporary workspace, and streams file changes back to the builder.
Install Claude Code
Have the Claude Code CLI installed and authenticated on your machine.
Run the bridge
Start the SleekWP agent server locally before opening the terminal in SleekAI.
Open New Terminal
SleekAI connects to the local bridge, mirrors the page, and starts Claude Code in that workspace.
Run this once in your local terminal
The bridge listens on ws://localhost:5733. When it is available, SleekAI can show the terminal option for supported page builders.
npx @sleekwp/agentCopy
For repeated use, install it globally with npm install -g @sleekwp/agent and run sleekwp-agent.
Mirrored page workspace
The page becomes a small project
SleekAI mirrors the active builder page into a per-element file tree, plus the schemas, global styles, and editing rules the agent needs. Claude Code can search, inspect, and edit it like any small project.
coding-agent-workspace
Search the page
Find copy, selectors, classes, and nearby elements with normal file search across the per-element tree.
Read structure
Walk parent-child relationships through the element folder layout, and read the area around the requested change.
Edit settings and CSS
Update an element's settings in element.json or its custom.css for the matching builder source field.
Read schemas first
Inspect schema/elements/{name}.json before creating unfamiliar element types so settings and defaults match.
Builder tools
Builder runtime, exposed as MCP tools
Each supported builder ships its own set of mcp__sleekwp__* tools the agent can call. Bricks, for example, exposes more than fifty tools across inspection, structure, styling, and the save flow. Elementor, Breakdance, and Beaver Builder ship their own equivalents.
Inspect
- mcp__sleekwp__get_page_structure
- mcp__sleekwp__get_selected_element
- mcp__sleekwp__get_element_tree
- mcp__sleekwp__find_elements_by_text
Edit
- mcp__sleekwp__update_element_settings
- mcp__sleekwp__set_element_text
- mcp__sleekwp__set_custom_css
- mcp__sleekwp__set_element_classes
Build
- mcp__sleekwp__create_element
- mcp__sleekwp__move_element
- mcp__sleekwp__duplicate_element
- mcp__sleekwp__delete_element
Save and validate
- mcp__sleekwp__validate_bricks_state
- mcp__sleekwp__save_page
- mcp__sleekwp__save_global_settings
- mcp__sleekwp__list_css_sources
MCP, in the editor
MCP brought into the open builder
SleekAI registers a sleekwp MCP server during the session. The agent calls per-builder runtime tools through it, so every action runs against the live editor in your browser instead of reaching for a server that does not see your unsaved state.
Tools that touch the live editor
MCP calls are dispatched through the open builder, so changes show up in the canvas immediately and respect any unsaved work the user already has open.
Standard MCP wiring
A normal .mcp.json is written into the workspace, with mcp__sleekwp__* on Claude Code's permission allowlist. Compatible with the rest of Claude Code's tool flow.
A close cousin of WebMCP
WebMCP is exploring how web apps can expose tools from the page itself so users and agents share context. SleekAI applies the same principle to WordPress page builders today.
What runs locally
Your page data stays on your machine
The bridge, the temporary workspace, and the file-change streaming all run on your computer. The browser talks to your local bridge; the bridge spawns a local Claude Code process. No external SleekAI server sits between them.
Workspace is local
Mirrored builder files live in a temporary directory created by @sleekwp/agent, not in your live theme or plugin folder.
Bridge stays on localhost
SleekAI connects to ws://localhost:5733 from the same browser. Builder data does not leave your network through the bridge.
Claude Code uses its own connection
Model calls go through your authenticated Claude Code CLI, not through the chat-feature API keys you set in SleekAI.
Agent workflow
The builder stays in the loop
SleekAI mirrors the active page for the coding agent, validates the changes that come back, and applies them through the builder. You review the result in the same editor session, not in a separate tool.
Start the bridge
@sleekwp/agent locally so SleekAI can connect the browser terminal to Claude Code.
Open the builder
Let Claude Code work
sleekwp MCP tools. The agent searches the workspace and calls runtime tools to make precise changes.
Review the result
Supported builders
One workflow, four builder bridges
The workflow is shared, but each builder bridge handles its own data model, CSS, validation, selected element state, and save flow.
Bricks
Element tree, CSS, selected state, structural rules, and Bricks-specific validation.
Elementor
Containers, widgets, responsive controls, page settings, and Elementor save flow.
Breakdance
Design tree, element settings, responsive values, page CSS, and validation.
Beaver Builder
Rows, columns, modules, settings, page CSS, and builder-specific save steps.
Example sessions
From prompt to applied edit
Each session reaches into the mirrored files and the builder runtime tools, then applies validated changes back through the live editor. Two builder bridges, side by side:
- · Calling find_elements_by_text for "Pricing", reading schema/elements/accordion.json
- · Calling create_element for accordion plus 6 entries
- ✓ Validated and applied to Bricks
- · Calling find_elements_by_type for "section"
- · Calling update_element_settings on 4 sections, mobile padding 80 → 40
- ✓ Validated and applied to Bricks
- · Calling get_selected_element, reading elements/01__hero/element.json
- · Calling add_container, moving children into a two-column layout
- ✓ Validated and applied to Elementor
- · Calling find_elements_by_text for "Free Trial"
- · Calling update_element_settings on 5 buttons
- ✓ Validated and applied to Elementor
Frequently Asked Questions
Claude Code is the first workflow SleekAI is focusing on because it already has strong file search, editing, and terminal habits. The mirrored workspace approach is broader than one model or one interface and can support other coding-agent workflows over time.
Coding agents work best when they can inspect structured context. The mirrored workspace gives the agent readable page content, the per-element folder tree, CSS, schemas, and editing rules so it can search and reason about the page rather than infer everything from visual context alone.
Yes. SleekAI registers a local sleekwp MCP server during the session and writes .mcp.json into the workspace. The agent calls per-builder runtime tools (mcp__sleekwp__create_element, mcp__sleekwp__validate_bricks_state, and so on) which are dispatched through the open builder rather than a separate server-side endpoint.
SleekAI gives the agent both files and MCP tools. File edits stream back through a watcher and apply to the matching builder source field. MCP tool calls are dispatched against the live builder runtime in the open browser tab. SleekAI validates before applying.
Claude Code is launched with --permission-mode acceptEdits, so file edits and the allowlisted mcp__sleekwp__* tools are auto-accepted. Save tools like save_page only run when the user explicitly asks the agent to save.
Yes. Start the local SleekWP agent bridge with npx @sleekwp/agent. It runs on your machine, connects SleekAI to Claude Code over ws://localhost:5733, and manages the temporary workspace.
The mirrored workspace lives in a temporary directory on your machine. The bridge listens on ws://localhost:5733 and spawns a local Claude Code process. No external SleekAI server sits between the browser and the agent. Claude Code itself reaches its model provider over your own CLI authentication.
Claude Code uses its own authentication and billing. SleekAI does not route Claude Code calls through the OpenAI, Anthropic, Google, or OpenRouter keys you configure for chat features. If your Claude Code CLI works in a normal terminal, it works inside the SleekAI coding-agent terminal.
Coding agents are available in beta across supported page builders. Core workflows are usable, but the context files, validation, terminal history, and builder-specific operations will continue to be refined from real usage.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout