How to Connect Wordpress to Gemini — via MCP

Connect WordPress to Gemini

WordPress is the world's most-used CMS. With AnythingMCP and Gemini, you can run editorial workflows — content refresh, SEO optimisation, scheduled publishing, internal linking, comment moderation — entirely with natural language.

What You Can Do

• "Find every post about 'machine learning' published over 6 months ago and refresh the top 5."
• "Update the Yoast meta description on post 412 to a 155-character summary."
• "Move all comments by 'Anonymous' on post 87 to spam."
• "Schedule a draft post titled 'September product update' for next Tuesday at 10 AM Europe/Berlin."
• "Walk me through your Site Health checks and tell me what to fix."

Setup

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

1. Generate a WordPress Application Password in /wp-admin/profile.php → Application Passwords. (HTTPS required.)
2. Open http://localhost:3000/connectors/store, import the WordPress adapter.
3. Supply WORDPRESS_URL, WORDPRESS_USERNAME, WORDPRESS_APP_PASSWORD.
4. Assign the connector to an MCP server.

Connect Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell) — anythingmcp should show as connected.
4. Start prompting — Gemini CLI can now call the WordPress tools.

Self-hosting with the quickstart above? Use your server's local endpoint http://localhost:4000/mcp/<server-id> as the URL.

Skill Tools (the AI-native edge)

Gemini reads only the tool list by default. When you ask "refresh stale content", Gemini calls wordpress_skill_content_refresh and receives the full step-by-step recipe on demand — listing the stalest posts, reading bodies, rewriting, persisting. This keeps the context window light and the workflow explicit.

Available skills:

• wordpress_skill_seo_content_pipeline
• wordpress_skill_content_refresh
• wordpress_skill_scheduled_publishing
• wordpress_skill_internal_linking
• wordpress_skill_media_optimization

SEO Meta (Yoast & Rank Math)

Call wordpress_list_seo_meta_keys to get a reference card of all the Yoast and Rank Math meta keys exposed via REST. Then use wordpress_update_post_meta to set them.

wordpress_update_post_meta(postId=42, meta={
  "_yoast_wpseo_metadesc": "A practical guide to ...",
  "_yoast_wpseo_focuskw": "wordpress ai workflows"
})

Rank Math uses rank_math_description, rank_math_focus_keyword, rank_math_title.

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Meta Muse