store_audit — ecommerce intelligence mcp server MCP Prompt
store_audit
is one of 1 prompt on the
ecommerce intelligence mcp server
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke store_audit from your client
- Claude Code ecommerce intelligence mcp server Prompt/store_audit run in your project directory
- Claude Desktop ecommerce intelligence mcp server Prompt/store_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ecommerce intelligence mcp server Prompt/store_audit ~/.cursor/mcp.json
- VS Code ecommerce intelligence mcp server Prompt/store_audit .vscode/mcp.json
- Zed ecommerce intelligence mcp server Prompt/store_audit ~/.config/zed/settings.json
- Windsurf ecommerce intelligence mcp server Prompt/store_audit ~/.codeium/windsurf/mcp_config.json
- Cline ecommerce intelligence mcp server Prompt/store_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ecommerce intelligence mcp server Prompt/store_audit ~/.gemini/settings.json
- Grok ecommerce intelligence mcp server Prompt/store_audit .mcp.json (in your project root)
- ChatGPT ecommerce intelligence mcp server Prompt/store_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai ecommerce intelligence mcp server Prompt/store_audit Settings → Connectors → Add custom connector
- LangChain ecommerce intelligence mcp server Prompt/store_audit pip install langchain-mcp-adapters
ecommerce intelligence mcp server also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.