Skip to main content
Glama
Sign In

WordPress MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted WordPress MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/wordpress-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data have nearly identical descriptions, both labeled 'Step 3 (FINAL)' and both requiring the same query_contexts preparation, making their boundary unclear. prompts_menu and query_contexts are more distinct, but the core action/query split is confusing.

Naming Consistency4/5

Three tools follow a clear verb_noun pattern (execute_action, query_contexts, query_data), while prompts_menu is a noun-first outlier. The deviation is minor and the overall convention remains readable.

Tool Count3/5

Four tools is thin for a WordPress MCP server, but the action-based gateway pattern partly justifies a compact surface. It sits at the borderline of under-scoped rather than clearly appropriate.

Completeness3/5

The dynamic action catalog may cover many WordPress operations, but the tool surface itself exposes no explicit create/update/delete lifecycle, and prompts_menu only browses prompts without management operations. Notable gaps remain for a server claiming broad WordPress coverage.

Available Tools

4 tools
execute_actionWordPress Execute ActionA
Destructive
Inspect

Execute WordPress action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

Inputs: body (required). Returns: object

prompts_menuWordPress PromptsA
Read-only
Inspect

Browse the WordPress prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsWordPress Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe WordPress data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, AND available_actions.

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataWordPress Data QueryA
Read-only
Inspect

Query WordPress data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.

Inputs: body (required). Returns: object

Tool Schema Changelog

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

    Related MCP Connectors

    Related MCP Servers

    • TanukiMCP

      AppleJax2
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for WordPress automation that enables users to manage content, themes, and site configurations using AI-driven workflows and the WordPress REST API. It provides a wide array of tools for site planning, management, and optimization compatible with tools like Cursor and Claude.
      49 npm
      1
      ISC

    • wp-mcp

      cnmbdb
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for WordPress content management via REST API, supporting posts, pages, media, comments, and terms through natural language interfaces like Cursor, ChatGPT, Codex, and Claude.
      14 npm
      MIT
    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources