PressBot MCP server · Model Context Protocol

WordPress, inside your IDE.

Connect Claude Code, Cursor, or Windsurf to your site and run 99 admin tools from your editor. No browser, no SSH — just the REST API you already have.

Get PressBot Pro How it works
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

Application Passwords, not OAuth.

Battle-tested WordPress Application Passwords, built into core since 5.6. Generate in your profile, paste into the client, revoke from the dashboard. HTTPS required.

application_passwords https_only revocable

Supported clients

Paste a config. You’re in.

Any MCP-capable editor. The list is growing fast — the ones below are tested end-to-end today.

Claude Code Anthropic Cursor Anysphere Windsurf Codeium Custom MCP client JSON-RPC

Connect

One JSON snippet. Three steps.

Enable MCP in PressBot → Settings → MCP Server. Generate an Application Password at Users → Profile. 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 same two things: the PressBot MCP endpoint and a WordPress Application Password (Users → Profile → Application Passwords). Here is the exact setup for each.

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 Windsurf to WordPress

Same JSON shape, one file: add the block under mcpServers in ~/.codeium/windsurf/mcp_config.json, then refresh servers from the Cascade panel.

~/.codeium/windsurf/mcp_config.json 
{
  "mcpServers": {
    "pressbot": {
      "serverUrl": "https://pressbot.io/wp-json/pressbot/v1/mcp",
      "headers": { "Authorization": "Basic YOUR_BASE64_TOKEN" }
    }
  }
}

Once connected, try: “List my draft posts”, “Which plugins need updates?”, or on Pro, “Write a post about our new opening hours and save it as a draft.” 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 7 read-only tools. Pro unlocks the full 99 and all downstream channels.

Capability Free Pro+
Visitor chatbot
MCP server · REST endpoint
Knowledge base exposed as MCP resources
Read-only MCP tools 7 tools
All 99 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 analytics in chat
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 99-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. 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 99 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, or Windsurf. Scheduled Automations are internal and recurring; Trusted Plans add a review step before risky changes go live.

Pricing

Same features. More sites.

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

Free

$0 · forever

MCP with 7 read-only tools

  • Visitor chatbot + product search
  • MCP server (read-only tools)
  • KB entries as MCP resources
Download free
Most popular

Pro · 1 site

$29 /yr

Full MCP + every Pro feature

  • All 99 MCP tools (read + write)
  • Admin agent in WordPress dashboard
  • Telegram bot + 7 alert types
  • Scheduled automations + trusted plans
  • Shield · WooCommerce · AI images
Get Pro

14-day money-back guarantee

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 (Anthropic), Cursor, Windsurf, and any custom MCP client. The list is growing fast as MCP becomes the default for AI-tool integration.

How is the MCP server authenticated?

WordPress Application Passwords over HTTPS. Generate a password at Users → Profile, add it to your MCP client config, and you’re connected. No custom API keys, no OAuth setup. Revoke access anytime from your WordPress dashboard.

Is MCP included in the free version?

Yes. Free includes an MCP server with 7 read-only tools (site info, posts, plugins, comments, conversations, booking availability, knowledge-base search) plus KB entries as MCP resources. Pro unlocks the full 99 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 99 tools. Use whichever fits your workflow — they’re completely independent.

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?

Most WordPress MCP adapters are thin, developer-oriented bridges: they expose raw REST endpoints and expect you to be comfortable with code or CLI setup. PressBot ships a production MCP server as part of a full AI plugin — 99 purpose-built tools with capability checks, Application Password auth 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.

01 Tool Reference

Every tool your MCP client can call

The full catalog behind the MCP server: content, SEO meta, WooCommerce, security, menus, media, and more.

Read the guide 02 Yoast SEO

Fix SEO meta from your AI editor

Audit and update Yoast titles, descriptions, and keyphrases through the same tools — from Claude Code or the dashboard.

Read the guide 03 Automations

When you want it running without you

MCP is for live sessions; scheduled automations with Trusted Plans handle the recurring work with approval built in.

Read the guide

Ready when you are

Your WordPress site, AI-native.

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

Get PressBot Pro Download free