WordPress MCP Server vs Memory

A side-by-side look at the WordPress MCP Server and Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

WordPress MCP Server logoWordPress MCP ServerOther Tools and Integrations · Local subprocess (stdio)MCP server for WordPress. Manage posts, users, comments, terms, metadata, and settings.41FairAuth: not declaredMemory logoMemoryOther Tools and Integrations · Local subprocess (stdio)Knowledge graph-based persistent memory system.89ExcellentAuth: no auth required

Verdict: choose WordPress MCP Server for other tools and integrations work as a local process; choose Memory for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

WordPress MCP Server logoChoose WordPress MCP Server when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: LOCAL_USERNAME, LOCAL_CONFIG, WP_DB_HOST, WP_DB_PORT, WP_DB_NAME, WP_DB_USER, WP_DB_PASSWORD, LOCAL_SSL_ENABLED.
Explore WordPress MCP Server

Memory logoChoose Memory when

  • You need dedicated capabilities in the Other Tools and Integrations domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You have the keys it needs: MEMORY_FILE_PATH.
  • You want tools like create_entities, create_relations, add_observations.
Explore Memory

Feature & specification comparison

Rows where the two servers differ are marked.

SpecWordPress MCP Server logoWordPress MCP ServerMemory logoMemory
CategoryOther Tools and IntegrationsOther Tools and Integrations
Quality signal41/100 · Fair89/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsLOCAL_USERNAMELOCAL_CONFIGWP_DB_HOSTWP_DB_PORTWP_DB_NAMEWP_DB_USERWP_DB_PASSWORDLOCAL_SSL_ENABLEDMEMORY_FILE_PATH
Verified ownerCommunity listing Verified
GitHub stars1091,540
Directory activity 1 views 0 installs 0 upvotes 9 views 0 installs 0 upvotes
ToolsNot listed9

Tools & capabilities

WordPress MCP Server tools

No tool names declared yet. Check the project README from the listing page.

Memory tools 9

  • create_entitiesCreate multiple new entities in the knowledge graph. An entity whose name already exists, or repeats an earlier entity in the same call, is skipped and its observations are not added; the result lists the skipped names in `skipped`. Use add_observations to add observations to an existing entity.
  • create_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voice
  • add_observationsAdd new observations to existing entities in the knowledge graph
  • delete_entitiesDelete multiple entities and their associated relations from the knowledge graph
  • delete_observationsDelete specific observations from entities in the knowledge graph
  • delete_relationsDelete multiple relations from the knowledge graph
  • read_graphRead the entire knowledge graph
  • search_nodesSearch for nodes in the knowledge graph based on a query
  • open_nodesOpen specific nodes in the knowledge graph by their names

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

WordPress MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wordpress-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@rnaga/wp-mcp"
      ],
      "env": {
        "LOCAL_USERNAME": "YOUR_LOCAL_USERNAME_HERE",
        "LOCAL_CONFIG": "YOUR_LOCAL_CONFIG_HERE",
        "WP_DB_HOST": "YOUR_WP_DB_HOST_HERE",
        "WP_DB_PORT": "YOUR_WP_DB_PORT_HERE",
        "WP_DB_NAME": "YOUR_WP_DB_NAME_HERE",
        "WP_DB_USER": "YOUR_WP_DB_USER_HERE",
        "WP_DB_PASSWORD": "YOUR_WP_DB_PASSWORD_HERE",
        "LOCAL_SSL_ENABLED": "YOUR_LOCAL_SSL_ENABLED_HERE"
      }
    }
  }
}

Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-memory"
      ],
      "env": {
        "MEMORY_FILE_PATH": "YOUR_MEMORY_FILE_PATH_HERE"
      }
    }
  }
}

Frequently asked questions

WordPress MCP Server is categorized under Other Tools and Integrations and uses a local stdio subprocess. Memory belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick WordPress MCP Server for other tools and integrations work and Memory for other tools and integrations.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

WordPress MCP Server has no declared pricing — check the project's own site. Memory is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add wordpress-mcp-server and memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, WordPress MCP Server has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 10 GitHub stars. Memory has 89/100 (Excellent) with 9 views, 0 installs and 91,540 GitHub stars.