Connect Cursor to WordPress with one mcp.json entry

Before you start

• AgentedSEO is active (WordPress 6.9 or later, PHP 8.1 or later), and you are an administrator.
• The site is on HTTPS. WordPress only offers application passwords over HTTPS.

Your endpoint speaks MCP over Streamable HTTP, a transport Cursor supports:

https://your-site.com/wp-json/agentedseo/mcp

01Create the agent’s password

1. Open AgentedSEO › Agents › Connections.
2. Under Connect an agent choose Desktop or code app.
3. Name your agent Cursor and click Create password. AgentedSEO creates the user agentedseo-cursor with the SEO Agent role and an application password, shown once.
4. Copy the config under Paste this config into your agent. Your password is already in it as a Basic Authorization header.

02Add the Cursor WordPress MCP entry

Paste the config. It already matches Cursor’s remote server format:

{
  "mcpServers": {
    "agentedseo": {
      "url": "https://your-site.com/wp-json/agentedseo/mcp",
      "headers": { "Authorization": "Basic <filled in by the Connections screen>" }
    }
  }
}

If the file has other servers, add the agentedseo entry inside the existing mcpServers.

Keep the password out of the repo

Cursor fills ${env:NAME} in url and headers. Set AGENTEDSEO_AUTH to the part after Basic , then save the file.

"headers": { "Authorization": "Basic ${env:AGENTEDSEO_AUTH}" }

03Check it in Cursor

• Open Customize in the sidebar and find agentedseo: toggle on, tools listed.
• If it fails, open the Output panel (Ctrl+Shift+U, Cmd+Shift+U on a Mac) and pick MCP Logs. A 401 means the header is wrong.

04Check it in WordPress

On AgentedSEO › Agents › Connections, click Run test. “Authorization header reaches WordPress” must pass. “Tools an agent is offered” shows how many tools Cursor sees. After its first request, Cursor shows under Connected agents.

05Your first safe task

1. The agent calls agentedseo-set-meta. Meta titles and descriptions ask first by default, so the answer is proposed. The live page has not changed.
2. Open AgentedSEO › Dashboard › Approvals. Check Before and After, the checks it passed and the agent’s note. Click Approve.
3. Open AgentedSEO › Dashboard › Change log, open the change’s Details and click Undo. The Before value is back, and the undo is logged.

06What Cursor’s agent can and can’t change

Cursor is where a lot of WordPress developers already work, so I kept the setup to one entry in a file you already have. The safety lives on the site, not in the editor.

Change the per-area defaults in AgentedSEO › Agents › Approval rules. Approving and rejecting are not tools: only a person can do them, in WordPress. Full table: what your agent can and can’t change.

Builder layouts (Bricks, Elementor, Breakdance, Oxygen) are read-only for agents, their SEO fields still change. Scripts and iframes in content are refused.

07Troubleshooting

08Questions about Cursor and WordPress

09Next steps