DEV Community

Mahdi JabinPour
Mahdi JabinPour

Posted on

Your First WordPress MCP Request Should Identify the Site

When a WordPress MCP server appears in your coding client's settings, it is tempting to jump straight to a real task. I would start with a much smaller request:

Identify the connected site and list the available tools. Do not make any changes.

I'm part of LumoWP, where we build Lumo Site Pilot, a WordPress-side bridge for compatible MCP clients. This is a practical connection-check workflow to use before editing through an assistant.

Registration is only one step

Adding a server entry tells the client where it should connect. You still need evidence that it can reach the endpoint, authenticate and return a useful result from the intended WordPress installation.

Those are different checks. A server name in a configuration screen doesn't prove all of them.

Our connection guide for WordPress, Codex and Claude Code explains the setup in more detail. Follow the instructions for your actual client and current plugin version instead of copying settings from an unrelated example.

Begin with site identity

Ask for the connected site's identity and tool list without requesting changes. Compare the response with the site you intended to work on, especially when you maintain production and staging installations with similar names.

If the response is missing, stop there. Check the endpoint, authentication and client configuration before combining connection troubleshooting with an editing task.

Define a small first task

Once the connection is confirmed, give the assistant a narrow inspection task. For example:

Inspect the selected page and explain what would need to change to update its contact section. Do not save anything yet.

Review the proposed scope before authorizing the actual edit. A useful instruction names the target, the desired result and the content that must stay unchanged.

Treat credentials according to their real authority

Selecting only read-oriented tools in a client is a workflow choice. It does not automatically reduce what the server credential can authorize. Keep keys out of prompts, shared screenshots and published configuration examples.

Take a suitable backup before changes. A connection tool is not a substitute for a recovery plan that covers the data you are about to modify.

Verify the result outside the assistant

After an authorized change, open the real page and test the relevant behavior. If the task touched a form, test the intended form flow. If it changed a layout, review the affected viewport sizes. The assistant reporting success is one piece of evidence, not the whole acceptance check.

A simple sequence is enough to remember:

  1. Confirm the intended site.
  2. Discover the available tools.
  3. Inspect a narrow target.
  4. Review and authorize a specific change.
  5. Verify the public result.

See Lumo Site Pilot and the MCP connection walkthrough for the product and setup details. Codex, Claude Code and other compatible clients are independent products; use the configuration supported by the client you actually run.

Top comments (1)

Collapse
 
ar9avg profile image
Arnav Gupta •

The credential-authority point deserves its own paragraph in every MCP setup guide. Selecting only read tools in the client filters what the model asks for, not what the token can actually do, and people conflate those two constantly. The identity-first check matters for the same reason: with production and staging side by side, a green config screen tells you a server responded, not that the right one did.