WEOMARKETLY DIVI MCP CONNECTOR
Connect a supported AI agent to WordPress and Divi, then use clear prompts to inspect or update approved site content.
Keep this guide open while you work. Every value in square brackets is a placeholder that your WEOMARKETLY connector administrator must replace.
Before you start
Gather the details below before changing any settings. Do not guess missing values.
- A supported AI agent installed on your computer.
- The connector setup details provided by your WEOMARKETLY administrator.
- The WordPress site address and an approved WordPress account.
- Permission to work on the intended site or staging environment.
Start on staging unless your project owner explicitly approves production. AI actions can change page content.
Choose your agent
Select your agent for the correct configuration location. The connector may be supplied as a local stdio command or a remote server URL. These are different connection methods; use only the one your administrator gives you.
Open Cursor settings, find Tools & MCP, and add the provided connector.
- Open Cursor Settings.
- Choose Tools & MCP.
- Add a new MCP server and use the matching configuration from Step 3.
Claude Desktop reads local MCP server settings from its desktop configuration file. Use the stdio command configuration supplied by your administrator.
- Open Claude Desktop settings.
- Open the developer configuration file.
- Add the stdio entry from Step 3, save the file, and restart Claude Desktop.
Check your agent’s MCP documentation before continuing. Confirm whether it supports local stdio, a remote MCP server URL, or both.
- Find the agent’s MCP server settings.
- Confirm the supported connection method.
- Translate the matching example from Step 3 without changing the supplied values.
Configure the connector
Choose one configuration method. Replace every square-bracket placeholder with an approved value. Keep credentials private.
Option A: Local stdio command
Use this when your administrator gives you a command that runs the connector on your computer. The agent launches the command and communicates with it through standard input and output.
{
"mcpServers": {
"weomarketly-divi": {
"command": "[COMMAND]",
"args": [],
"env": {
"WP_URL": "[WP_URL]",
"WP_USERNAME": "[WP_USERNAME]",
"WP_APP_PASSWORD": "[WP_APP_PASSWORD]"
}
}
}
}Option B: Remote server URL
Use this only when your agent supports remote MCP servers and your administrator provides a server
URL. A remote URL is not a command and should not be placed in the command field.
{
"mcpServers": {
"weomarketly-divi": {
"url": "[SERVER_URL]"
}
}
}Never paste WordPress passwords, application passwords, or private server details into chat, tickets, screenshots, or this guide. Store them only in the approved agent configuration.
Connect WordPress
For a local stdio setup, replace the WordPress environment placeholders with the values supplied for the intended site. Remote setups may handle access on the server; follow the instructions from your administrator instead of adding unsupported fields.
[WP_URL]- The full address of the approved WordPress site.
[WP_USERNAME]- The approved WordPress account name.
[WP_APP_PASSWORD]- An application password created for the approved account, if your connector setup requires it.
Save the configuration. Restart the agent if it does not reload MCP settings automatically.
Test the connection
Start with a read-only request. This confirms the site before any content is changed.
Using the WEOMARKETLY DIVI connector, identify the connected WordPress site and list the five most recently updated pages. Do not make any changes.
A successful response should name the expected site and return page information without an edit.
Stop if the agent names the wrong site, cannot identify the site, or requests credentials in chat. Recheck the setup with your administrator.
Ready-to-use prompts
Copy a prompt, replace the square-bracket placeholder, and review the agent’s plan before approving an edit.
Using the WEOMARKETLY DIVI connector, review the page titled “[PAGE_TITLE]”. Summarize its current sections and flag any missing calls to action. Do not make changes.
Using the WEOMARKETLY DIVI connector, prepare an update plan for the page titled “[PAGE_TITLE]” based on this approved brief: “[APPROVED_BRIEF]”. Show the proposed changes before editing.
Using the WEOMARKETLY DIVI connector, inspect the page titled “[PAGE_TITLE]” after the approved update. Confirm the requested content is present and list anything that still needs review. Do not make more changes.
Frequently asked questions
Why does the connector show as unavailable?
Check that you used the correct connection method, replaced every placeholder, and restarted the
agent after saving. For a local setup, confirm that [COMMAND] was replaced with the
exact command supplied by your administrator.
Can I use the remote URL in Claude Desktop?
This guide does not assume remote URL support in Claude Desktop. Use the local stdio configuration your administrator provides, or confirm current support in the official agent documentation.
Where should I put my WordPress application password?
Put it only in the approved local configuration field when your setup requires it. Do not paste it into an agent conversation or share it in a screenshot.
Can I connect directly to the production site?
Only with explicit project approval. Use staging for setup and testing whenever it is available.
What should I do before approving an edit?
Confirm the site, page, requested changes, and scope. Ask the agent to show its plan first, then review the page again after the change.
Support
Contact Bob Salazar for connector setup questions. Include the agent name, the step where you stopped, and a screenshot with all private values hidden.
These support links are placeholders. Replace them with approved team destinations before publishing.
View locally
You can open index.html directly in a browser. For the most reliable local preview, start
a static server in the mcp-docs folder:
python3 -m http.server 4177Then open http://localhost:4177. No installation or build step is required.