Set up Cursor
Cursor connects to DocxToWP straight from its MCP settings, with no helper to install.
Before you start
- DocxToWP Pro 1.6.0 or later, with your licence active.
- Cursor, recent enough to have MCP support in its settings.
- In WordPress, DocxToWP Pro → AI Agents: the connection switched on and a key created. See Connect an AI agent.
1. Add DocxToWP to mcp.json
For one project, create or open .cursor/mcp.json in that project. For every project, use ~/.cursor/mcp.json in your home folder. Paste the snippet from DocxToWP Pro → AI Agents → Connect apps → Cursor. It looks like this:
{
"mcpServers": {
"docxtowp": {
"url": "https://your-site.com/wp-json/docxtowp/v1/mcp",
"headers": {
"Authorization": "Bearer dwpk_…"
}
}
}
}If the file already has mcpServers, add only the "docxtowp" entry. Keep this file out of public repositories: it holds your key.
2. Check it
Open Cursor Settings → MCP. DocxToWP should show a green dot and four tools. If it shows red, click it to see the error.
3. Ask in Agent mode
Open the chat (Ctrl+L, or Cmd+L on a Mac) and make sure it is in Agent mode, not Ask. Paste a prompt from the Prompt library, such as Markdown Publisher, and accept the tool runs when Cursor asks. It returns the edit and preview links of the new draft.
Cursor is handy for a folder of Markdown notes: ask it to send each .md file in a folder to WordPress as a draft, one at a time.
If something goes wrong
- A key error with the right key: replace
"Authorization": "Bearer dwpk_…"with"X-API-Key": "dwpk_…". - The tools do not appear in the chat: check Agent mode is selected, and that DocxToWP is switched on in Cursor Settings → MCP.
- More messages and fixes: Connect an AI agent → If it does not connect.
Disconnect
Remove the "docxtowp" entry from mcp.json and revoke the key in DocxToWP Pro → AI Agents → Keys.
Still stuck? Email support@docxtowp.com and we will walk you through it.