PressBot MCP server · Model Context Protocol

A free WordPress MCP server, inside your IDE.

The read-only MCP server is free in the PressBot plugin: connect Claude Code, Cursor, Codex, or any MCP-compatible agent and ask about your site. Pro adds write tools, up to 132 admin tools in total. Sign in with OAuth where your client supports it, or use a WordPress Application Password.

or download the zip

Free: read tools OAuth or Application Passwords JSON-RPC 2.0 No server config

What is MCP

An open standard, spoken natively.

Model Context Protocol is the emerging standard for AI clients to talk to external tools. PressBot implements it so your WordPress site speaks the same language as your IDE.

01 / Open protocol

No vendor lock-in.

MCP is backed by Anthropic and implemented by a growing list of clients. Connect any compatible AI agent — today or later — without rewriting integrations.

json-rpc 2.0 initialize tools/list

02 / Streamable HTTP

Runs on your REST API.

Standard HTTP transport on the endpoints WordPress already exposes. No SSH, no ports, no server-side daemons. If your site loads, MCP works.

wp-json/pressbot/v1/mcp shared_hosts_ok

03 / Native WordPress auth

Sign in with OAuth, or use an Application Password.

For MCP clients that support it, paste the server URL, sign in to WordPress, and approve. For config-file clients, use an Application Password (built into WordPress core since 5.6). Both are revocable from WordPress. HTTPS required.

application_passwords https_only revocable

Supported clients

Paste a config. You’re in.

Any MCP-capable coding agent or IDE. The list keeps growing — Claude Code, Cursor, and Codex are tested end-to-end today.

Claude Code Anthropic Cursor Anysphere Codex OpenAI Custom MCP client JSON-RPC

Connect

One JSON snippet. Three steps.

Enable MCP in PressBot → Settings → MCP Server. Connect by OAuth sign-in, or generate an Application Password at Users → Profile and paste the config. That’s it.

~/.mcp/config.json
// replace app_password with the one you generated in Users → Profile
{
  "mcpServers": {
    "pressbot": {
      "url": "https://pressbot.io/wp-json/pressbot/v1/mcp",
      "headers": {
        "Authorization": "Basic BASE64(you:app_password)"
      }
    }
  }
}

Client walkthroughs

Your editor, connected in two minutes.

Every client needs the PressBot MCP endpoint and a way to sign in: OAuth where the client supports it, or a WordPress Application Password (Users → Profile → Application Passwords) for config-file clients like the ones below. Here is the exact setup for each. For token tips, several sites, and troubleshooting, see the full Cursor and Claude Code tutorial, or how PressBot compares to other WordPress MCP servers.

Connect Claude Code to WordPress

One command in your terminal. Claude Code registers the server and discovers every tool your plan allows.

terminal
# base64-encode "username:app password" first:  echo -n 'you:xxxx xxxx xxxx xxxx' | base64
claude mcp add pressbot "https://pressbot.io/wp-json/pressbot/v1/mcp" \
  --transport http \
  --header "Authorization: Basic YOUR_BASE64_TOKEN"

Connect Cursor to WordPress

Add the server to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally), then enable it under Settings → MCP.

.cursor/mcp.json
{
  "mcpServers": {
    "pressbot": {
      "url": "https://pressbot.io/wp-json/pressbot/v1/mcp",
      "headers": { "Authorization": "Basic YOUR_BASE64_TOKEN" }
    }
  }
}

Connect Codex to WordPress

Add the server to ~/.codex/config.toml (used by the Codex CLI and IDE extension), or run codex mcp add from your terminal. Restart Codex and run /mcp to confirm PressBot is connected.

~/.codex/config.toml
# base64-encode "username:app password" first:  echo -n 'you:xxxx xxxx xxxx xxxx' | base64
[mcp_servers.pressbot]
url = "https://pressbot.io/wp-json/pressbot/v1/mcp"
http_headers = { Authorization = "Basic YOUR_BASE64_TOKEN" }

Once connected, try: “List my draft posts”, “Which plugins need updates?”, “What were my top search queries last month?” (Search Console), or on Pro, “Use run_content_pipeline to draft a post about our new opening hours, then poll until the draft is ready.” The full catalog is on the tools page.

Free vs Pro

Free gives you read. Pro gives you write.

The free tier is a fully-working MCP server with 16 read-only tools. Pro unlocks the full 132 and all downstream channels.

Capability Free Pro+
Visitor chatbot
MCP server · REST endpoint
Knowledge base exposed as MCP resources
Read-only MCP tools 16 tools
All 132 MCP tools (read + write)
Admin agent in WordPress dashboard
Telegram bot
WooCommerce admin tools
AI Visibility audits (GEO/AEO)
Yoast SEO admin-agent tools
Advanced Custom Fields admin-agent tools
Shield — AI login protection
GA4 & Search Console analytics
Cloudflare status (read-only)
Cloudflare report & changes (manage_cloudflare)
Your AI app writes the Analytics AI overview with its own model (facts, then save; every number checked)
Scheduled automations & trusted plans

Under the hood

Same tools. Four channels.

MCP, the dashboard agent, the Telegram bot, and the visitor chatbot share the same 132-tool execution pipeline — one permission model, one audit trail.

PressBot registers one REST endpoint at /wp-json/pressbot/v1/mcp that speaks JSON-RPC 2.0. An AI client calls initialize to discover capabilities, then tools/list to pull every tool with full JSON Schema parameter definitions.

Each tool maps to a real WordPress operation — creating posts, managing plugins, running security audits, querying Woo orders, pulling GA4 traffic or Search Console queries. The client calls tools/call with structured arguments; PressBot executes through the same ToolExecutor pipeline as the dashboard agent and Telegram bot, with identical capability checks and safety guardrails.

Your knowledge base is exposed as MCP resources via resources/list and resources/read. The client reads the resource, understands the context, then executes tools with that knowledge.

initialize

Server name, version, protocol version, and supported capabilities (tools + resources).

tools/list

Returns all 132 tools with JSON Schema input definitions. Destructive tools are annotated.

tools/call

Execute a tool by name with arguments. Same capability checks as the dashboard agent.

resources/list

Knowledge-base entries available as context. URIs like pressbot://kb/return-policy.

resources/read

Fetch a knowledge-base entry’s full content in markdown.

MCP vs Automations

MCP is interactive and external — you drive work from Claude Code, Cursor, Codex, or any other MCP agent. Scheduled Automations are internal and recurring; Trusted Plans add a review step before risky changes go live.

Content pipeline (Pro)

run_content_pipeline queues research, write, critic, optional image, and categorize, then always saves a draft — never publishes. The call returns a job id immediately so MCP clients are not held open for a multi-minute run; poll status until the draft exists.

Pricing

Same features. More sites.

MCP is included on every paid tier with all 132 tools. Pick by how many sites you run.

Free

$0 · forever

MCP with 16 read-only tools

  • Visitor chatbot + product search
  • MCP server (read-only tools)
  • KB entries as MCP resources
Get it on WordPress.org

or download the zip

Business · 5 sites

$59 /yr

Same features, more sites

  • All Pro features
  • Up to 5 site activations
  • Priority support
Get Business

14-day money-back guarantee

Agency · 50 sites

$99 /yr

Scale to all your clients

  • All Pro features
  • Up to 50 site activations
  • Priority support
Get Agency

14-day money-back guarantee

14-day money-back guarantee · cancel anytime

FAQ

Honest answers.

What AI clients work with PressBot MCP?

Any client that speaks the Model Context Protocol: Claude Code, Cursor, Codex, and the growing list of MCP-compatible coding agents. If your tool supports MCP over HTTP, it can use PressBot.

How is the MCP server authenticated?

Two ways, both over HTTPS. OAuth sign-in for MCP clients that support it: paste the server URL, sign in to WordPress, and approve. Or an Application Password for config-file clients like Claude Code, Cursor, and Codex: generate one at Users → Profile and add it to your client config. Either way you can revoke access anytime from WordPress.

Is MCP included in the free version?

Yes. Free includes an MCP server with 16 read-only tools (site info, posts, plugins, comments, conversations, booking availability, knowledge-base search, Site Check, Cloudflare status, plus provider-free maintenance tools: baseline, recent changes, change timeline, health probe, and change-risk assessment) plus KB entries as MCP resources. Pro unlocks the full 132 tools including writes, admin agent, Telegram, and all integrations.

How is MCP different from Scheduled Automations?

MCP is for live, operator-driven work from external AI clients like Claude Code or Cursor. Scheduled Automations are for recurring jobs that run inside WordPress on a schedule, and Trusted Plans let those recurring jobs pause for your approval before risky changes go live.

Does MCP require special server configuration?

No. PressBot MCP runs over your existing WordPress REST API. If your site loads, MCP works — no SSH access, no port configuration, no server-side dependencies. Shared hosting, VPS, and managed WordPress hosts all supported.

Can I use MCP and the admin agent at the same time?

Absolutely. MCP, the admin dashboard agent, the Telegram bot, and the visitor chatbot are all access channels to the same 132 tools. Use whichever fits your workflow — they’re completely independent.

Can MCP write a full blog post?

Yes on Pro. Call run_content_pipeline with a writing prompt. PressBot queues the full pipeline (research, write, critic, optional image, categorize) and always saves a draft — it never publishes. The call returns a job id right away so your MCP client does not hang on a long run; poll status until the draft is ready.

What happens with destructive operations?

Tools that delete content or modify critical settings are annotated as destructive in the MCP tool schema. Clients like Claude Code have their own confirmation flows and will ask before executing them.

How is PressBot different from other WordPress MCP plugins and adapters?

PressBot works alongside the official WordPress MCP Adapter: it registers five PressBot abilities there (AI visibility audits, knowledge search and Trusted Plans you review), so Adapter-based clients can use them. Its own built-in server goes further. PressBot ships a production MCP server as part of a full AI plugin — 132 purpose-built tools with capability checks, OAuth sign-in or Application Password auth, both managed from your WordPress dashboard, destructive-action annotations, and your knowledge base exposed as MCP resources. The same tools also power the admin agent and Telegram bot, so nothing works differently between channels. No composer, no node, no proxy server to babysit.

Keep exploring

MCP is one channel. Same agent everywhere.

Everything your MCP client can do is also available in the WordPress dashboard, on Telegram, and on a schedule.

Ready when you are

Your WordPress site, AI-native.

132 tools exposed via MCP. Connect from any client. Drive your site with natural language.

or download the zip