Guide

MCP server

2 min read 220 words Updated 14 August 2026

wpmcp speaks the Model Context Protocol over stdio, so Claude and other assistants can inspect and export a WordPress site without a shell between them. Eight tools cover site information, listings, a single post and a full export in any supported format.

Claude Desktop Configuration (claude_desktop_config.json):

1{
2  "mcpServers": {
3    "wpexporter": {
4      "command": "wpmcp",
5      "args": ["serve"]
6    }
7  }
8}

Claude Code Configuration (.claude/mcp.json):

1{
2  "mcpServers": {
3    "wpexporter": {
4      "type": "stdio",
5      "command": "wpmcp",
6      "args": ["serve"]
7    }
8  }
9}

Available MCP Tools:

Tool	Description
`list_formats`	List all 14 available export formats
`get_site_info`	Get WordPress site information
`list_posts`	List posts with optional path filtering
`list_pages`	List pages from a site
`export_site`	Full site export to any format
`get_post`	Get a specific post by ID
`list_categories`	List all categories
`list_media`	List media files

export_site writes the same tree the CLI does, reader comments included, and reports the counts back to the caller — an agent has no console to read warnings from, so stats.comments is where a site whose comment route is closed shows up as a zero. noPosts, noPages, noProducts and noComments switch a collection off, matching the --no-… flags in the CLI reference.