Skip to main content
Glama

dapper-mcp-wp

An MCP server that lets Claude (Claude Code, Claude Desktop, claude.ai) connect to your WordPress sites and read context, create pages, and edit pages — instead of copy-pasting into the admin by hand.

Built for the builders you actually use: WPBakery / Visual Composer, Gutenberg, and Classic — all of which keep content in post_content, so they're fully editable over the standard WordPress REST API. No companion plugin required.

Elementor stores layout as JSON in post meta and needs a companion plugin to edit safely — that's a later phase, not part of this REST-only core.

How it works

Claude  ──MCP──>  dapper-mcp-wp  ──REST + App Password──>  WordPress site(s)
                  (this server)
  • Auth: WordPress core Application Passwords (Settings → Users → your bot user). Scoped, revocable, never exposes a real login.

  • Safety: new pages default to draft; edits rely on WordPress revisions (every save is auto-versioned → one-click rollback).

  • Context: get_site_context reports theme, plugins, detected builder, and recent pages. Pair it with a hand-maintained profile in sites/.

Related MCP server: AutoWP MCP Server

Setup

  1. Install deps & build

    npm install
    npm run build
  2. Create the bot user on each site In WP admin: add a user (e.g. dapper-bot, role Editor or Admin) → edit the user → Application Passwords → add one → copy the generated password.

  3. Add the connection — copy the example and fill in real values:

    cp sites.example.json sites.local.json   # sites.local.json is gitignored
    [
      { "name": "acme", "url": "https://acme.example.com",
        "username": "dapper-bot", "appPassword": "xxxx xxxx xxxx xxxx xxxx xxxx" }
    ]
  4. Smoke-test the connection

    npm run doctor
  5. Point Claude Code at it (.mcp.json in a project, or your user config):

    {
      "mcpServers": {
        "dapper-wp": { "command": "node", "args": ["dist/index.js"] }
      }
    }

    (Use an absolute path to dist/index.js, or tsx src/index.ts during dev.)

Tools

Tool

What it does

list_sites

List configured sites

get_site_context

Auth check + theme, plugins, builder, recent pages

list_pages

List/search pages

get_page

Fetch one page's raw editable content

create_page

Create a page (draft by default)

update_page

Edit title/content/status (revision-safe)

Roadmap

  • Phase 1 (here): REST-only core for WPBakery / Gutenberg / Classic.

  • Phase 2: get_design_tokens (colors/fonts), richer per-site profiles, WPBakery shortcode helpers imported from the skill file.

  • Phase 3: optional dapper-connector WP plugin — one-click onboarding (auto-provision bot user + App Password) and Elementor/Divi support.

Security

sites.local.json and .env are gitignored. Never commit site credentials. Each site's Application Password can be revoked independently from WP admin.

Available Tools

6 tools
create_pageB

Create a new page. Defaults to DRAFT so it can be previewed before going live.

Inputs: site (required), title (required), content (required), slug, +1 more.

get_pageB

Fetch one page's raw content (the editable source: shortcodes / blocks / HTML).

Inputs: id (required), site (required).

get_site_contextA

Bring Claude up to speed on a site: confirms auth, reports active theme, plugins, detected page builder, and a sample of recent pages.

Inputs: site (required).

list_pagesB

List pages on a site, optionally filtered by a search term.

Inputs: site (required), search, per_page.

list_sitesA

List the WordPress sites this server is configured to connect to.

Inputs: no named parameters.

update_pageA

Update an existing page's title/content/status. WordPress auto-saves a revision on every change, so edits are rollback-safe. Omit status to keep current state.

Inputs: id (required), site (required), title, status, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: page CRUD (create, read, update, list) plus site context and site listing. No overlaps or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_page, list_sites), making them predictable and easy to understand.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose (WordPress page editing), covering essential operations without unnecessary bloat or insufficiency.

    Completeness4/5

    CRUD for pages is mostly covered (create, read, update, list), but missing a delete_page tool, which could be a minor gap. Site context and listing are included.

    Related MCP Connectors

    Related MCP Servers