get_store_performance — Fudge for Shopify MCP Tool Read-only
get_store_performance
(get store performance) is one of 57 tools on the
Fudge for Shopify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_store_performance from your client
- Claude Code Fudge for Shopify get_store_performance run in your project directory
- Claude Desktop Fudge for Shopify get_store_performance ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Fudge for Shopify get_store_performance ~/.cursor/mcp.json
- VS Code Fudge for Shopify get_store_performance .vscode/mcp.json
- Zed Fudge for Shopify get_store_performance ~/.config/zed/settings.json
- Windsurf Fudge for Shopify get_store_performance ~/.codeium/windsurf/mcp_config.json
- Cline Fudge for Shopify get_store_performance ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Fudge for Shopify get_store_performance ~/.gemini/settings.json
- Grok Fudge for Shopify get_store_performance .mcp.json (in your project root)
- ChatGPT Fudge for Shopify get_store_performance Settings → Connectors → Advanced → Developer mode
- Claude.ai Fudge for Shopify get_store_performance Settings → Connectors → Add custom connector
- LangChain Fudge for Shopify get_store_performance pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http fudge https://mcp.fudge.ai/mcpOther tools on this server
- list_stores
- connect_store
- get_store_overview
- search_design_references
- show_design_references
- get_store_insights
- get_design_guide
- search_guides
- read_guide
- find_context
- remember
- record_change
- read_store_document
- edit_store_document
- create_store_document
- create_plan
- list_store_audits
- run_ai_readiness_check
- run_catalog_data_audit
- run_knowledge_base_check
- get_store_audit_result
- check_page_speed
- check_store_technical
- check_page
- start_website_redesign
- start_store_builder
- check_catalog_data
- search_catalog
- list_offers
- capture_page
- get_keyword_metrics
- find_keyword_ideas
- get_search_results
- get_ranked_keywords
- list_work
- read_work
- message_fudge
- stop_work
- request_publish_review
- open_fudge_home
- show_draft
- start_draft
- read_draft_file
- search_draft_files
- edit_draft_file
- write_draft_file
- delete_draft_file
- edit_draft_content
- create_draft_product
- create_draft_collection
- create_draft_page
- create_draft_article
- show_preview_consent
- set_preview_consent
- send_feedback
- show_resources
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.