Want Cursor to work with a hosted WordPress site without maintaining a local copy? The important part is giving it a real connection to the site, then checking what that connection allows.
This walkthrough uses Lumo Site Pilot, our WordPress plugin. It exposes an MCP endpoint that compatible clients such as Cursor can connect to. This is an independent LumoWP product, not an official Cursor or WordPress integration.
1. Connect the site, not just a rule file
Install Site Pilot on the WordPress site you intend to manage. Use the endpoint and connection key supplied by your installed version, and add that connection to your client's MCP configuration. Follow the plugin's current connection instructions rather than copying someone else's domain or key.
A rule file describes how you want the assistant to work. It is not the transport and cannot, by itself, authenticate a connection.
2. Start with a read-only check
Before requesting changes, try a small inspection task:
Check the connection and list the available tools. Then summarize the
WordPress version, active plugins and current site status. Do not change anything.
If the connection fails, check the endpoint, key and hosting restrictions before proceeding. If an expected tool is absent, do not assume the assistant has that capability.
3. Keep working instructions separate from credentials
Keep keys out of committed rules, public screenshots and chat transcripts. A useful project instruction is:
Read the current state before editing. Explain the proposed change.
Back up before a write. Make one change at a time, verify it, and report
what changed. Do not send customer messages or expose customer data.
Start on a staging site where possible. A successful tool response is not proof that checkout, forms or page layouts still work.
4. Use specific prompts
Instead of asking the assistant to fix everything, give it a narrow task:
- Inspect the error log and explain the likely cause before editing files.
- Identify plugins with available updates and propose a staged update plan.
- Review one custom plugin, propose a patch and explain how to test it.
- Check a setting and report its current value without changing it.
Review the result in WordPress and in the browser. Test the user journey affected by the change, such as submitting a form or completing a test checkout.
Is this the right approach for your site?
It can fit a remote administration workflow when you want an MCP client to inspect or manage WordPress. It does not replace backups, version control or review, and available tools depend on the plugin version and configuration.
The current connection instructions and demo are on the Lumo Site Pilot product page.
What is the first task you would want to inspect from Cursor: plugin errors, site settings or a custom feature?
Cover illustration generated with AI.
Top comments (3)
finally someone showed how to do this without messing around with ssh keys lol
finally a way to do this without messing around with ssh keys lol. does this work with basic cpanel hosting too?
That’s the idea — one connection key, no SSH. It runs as a normal WordPress plugin over HTTPS, so basic cPanel hosting is fine as long as you can install plugins, PHP is 8.1+, and the WordPress REST API is not blocked. You don’t need SSH or terminal access. If you try it on a host and something is locked down, tell me what the host shows and I’ll point you to the setting.