Skip to main content
Glama
Sign In

WooCommerce MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted WooCommerce 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/woocommerce-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are both presented as the final workflow step with nearly identical preconditions, making it unclear when to execute versus query. query_contexts also overlaps as a planning/discovery helper, so tool boundaries rely heavily on subtle wording rather than distinct purposes.

Naming Consistency3/5

Three tools use a verb_noun pattern (execute_action, query_contexts, query_data), but prompts_menu breaks the convention with a noun_noun-style name. The set is readable, but the naming is not fully predictable.

Tool Count4/5

Four tools is within a reasonable range and each has an apparent role in the workflow. However, the surface is quite lean for a broad WooCommerce integration and depends on generic action dispatch rather than more explicit operations.

Completeness4/5

The set includes discovery of accounts/actions, querying, execution, and prompt browsing, which can cover many WooCommerce workflows via generic actions. Minor gaps remain around explicit resource lifecycle operations and prompt usage, but the core surface is broadly workable.

Available Tools

4 tools
execute_actionWooCommerce Execute ActionA
Destructive
Inspect

Execute WooCommerce 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_menuWooCommerce PromptsA
Read-only
Inspect

Browse the WooCommerce 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_contextsWooCommerce Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe WooCommerce 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_dataWooCommerce Data QueryA
Read-only
Inspect

Query WooCommerce 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.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • mcp-server-woocommerce

      AmitGurbani
      A
      license
      B
      quality
      D
      maintenance
      MCP server for managing WooCommerce stores through AI assistants like Claude. Provides 101 tools covering products, orders, customers, coupons, shipping, taxes, webhooks, settings, reports, and more.
      100
      112 npm
      2
      MIT

    • Urumi MCP Gateway

      kazuma761
      A
      license
      Not graded
      quality
      C
      maintenance
      Puts every MCP server a team uses behind a single /mcp endpoint, so clients like Claude Code, Codex, and Cursor reach all aggregated tools with one personal, revocable API key while upstream credentials stay hidden. It routes each call to the right upstream, enforces per-tool permissions, isolates failures, and writes an audit log of who called what, with a bundled WooCommerce server for products and orders.
      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