Skip to main content
Glama
Sign In

Magento MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

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

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation3/5

execute_action and query_data are the main ambiguity: both are labeled Step 3 (FINAL), require the same query_contexts prerequisites, and tell the agent to construct a body from available actions. Their names hint at write/execute versus read/query, but the descriptions do little to clarify the boundary.

Naming Consistency4/5

Three tools follow a verb_noun pattern (execute_action, query_contexts, query_data), while prompts_menu is noun-based. The deviation is minor and the names remain readable and predictable overall.

Tool Count5/5

Four tools is well-scoped for a generic Magento action/query server: discovery, execution, data querying, and prompt browsing each have a role. The dynamic action catalog keeps the surface compact rather than listing every Magento operation separately.

Completeness4/5

The generic execute/query dispatcher can cover Magento reads and writes if available_actions is comprehensive, and prompt browsing is included. Direct explicit CRUD tools are absent, but the catalog-driven pattern is a reasonable workaround.

Available Tools

4 tools
execute_actionMagento Execute ActionA
Destructive
Inspect

Execute Magento 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_menuMagento PromptsA
Read-only
Inspect

Browse the Magento 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_contextsMagento Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Magento 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_dataMagento Data QueryB
Read-only
Inspect

Query Magento 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

    • Magector

      krejcif
      A
      license
      A
      quality
      B
      maintenance
      Technology-aware MCP server for Magento 2 and Adobe Commerce with intelligent indexing and search, enabling AI assistants to search, navigate, and understand codebases via semantic search and domain-specific pattern detection.
      47
      49 npm
      20
      MIT
    • wptaskify MCP server

      wptaskify MCP serverofficial

      logicaldottech
      F
      license
      Not graded
      quality
      C
      maintenance
      A hosted MCP server that lets AI clients manage WordPress sites, WooCommerce and Shopify stores, Pinterest accounts and Google Search Console, covering content, products, orders, themes, analytics and SEO fields through OAuth sign-in. Risky operations such as deletes, refunds and theme switches are held until a person approves them.
      -
    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