Shopify Theme Inspector MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check if the Shopify Theme Inspector MCP server is running correctly |
| loginA | Authenticate with Shopify via OAuth2 (same method as the Chrome Theme Inspector extension). Opens a browser for you to log in. This provides full flame graph profiling data. |
| login_in_chromeA | Start Shopify OAuth in the user's existing Chrome profile without closing Chrome. After authorization, copy the full final callback URL and pass it to complete_login_in_chrome. |
| complete_login_in_chromeA | Complete a login_in_chrome flow using the full final chromiumapp.org callback URL copied from Chrome's address bar. |
| login_legacyA | Legacy cookie-based Shopify login. Opens browser for manual login. Required for 'analyze_liquid_file' tool which needs Admin API access. Use 'login' (OAuth2) for profiling tools. |
| logoutA | Remove saved authentication (both OAuth2 and legacy sessions) for a Shopify store |
| get_auth_statusA | Check authentication status. Shows both OAuth2 (for profiling) and legacy (for Admin API) authentication. |
| profile_pageA | Profile a Shopify store page to analyze Liquid template rendering performance. Returns FULL flame graph profiling data (same as Chrome extension). Requires OAuth2 authentication first (use the 'login' tool). |
| get_profile_summaryA | Profile a Shopify store page and return a structured performance summary with top slow nodes and template breakdown. More readable than raw profile_page data. Requires OAuth2 authentication first. |
| find_slow_templatesC | Identify Liquid templates and sections that are taking longer than a specified threshold to render. Requires OAuth2 authentication. |
| get_bottlenecksA | Profile a page and automatically detect performance anti-patterns. Returns prioritized recommendations with severity ratings (critical/warning/info), specific file/line locations, measured impact, and concrete fix suggestions. This is the BEST tool for identifying what to optimize. |
| analyze_liquid_fileA | Statically analyze a specific Liquid file for performance anti-patterns. Requires legacy cookie authentication (use 'login_legacy' tool). |
| compare_pagesA | Profile two pages on the same store and compare their performance side-by-side. Shows differences in render time, template breakdown, and recommendations. Great for A/B testing template changes or comparing product vs collection page performance. |
| batch_profileA | Profile multiple pages on the same store in a single call. Returns a summary comparison of all pages sorted by render time. Useful for finding the slowest pages on a site. Maximum 10 pages per call. |
| get_profile_historyA | View profiling history and performance trends for a store. Shows how render times have changed over time. Every profiling call is automatically saved to history. Use this to track the impact of optimizations. |
| export_profileA | Profile a page and export the results in a specified format. Supported formats: 'speedscope' (JSON for speedscope.app visualization), 'csv' (spreadsheet-friendly), 'markdown' (shareable report with tables, recommendations, and severity badges). Can save to a file or return inline. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools have distinct purposes, but there is potential confusion among the four login methods (login, login_in_chrome, complete_login_in_chrome, login_legacy) and among profiling tools (profile_page, get_profile_summary, get_bottlenecks, export_profile) that all profile a page. Descriptions clarify differences, but the overlap requires careful reading.
Tool names generally follow a verb_noun pattern (e.g., get_profile_summary, find_slow_templates, export_profile), but there are minor inconsistencies: some use 'get_' prefixes, others don't (profile_page vs. get_profile_summary), and multi-word names like login_in_chrome and complete_login_in_chrome break the simple pattern. Still readable and predictable overall.
With 16 tools, the server is slightly over the typical well-scoped range of 3-15, but the count is justified by the broad feature set including authentication, profiling, batch operations, comparison, export, history, and health checks. Each tool serves a distinct function in the domain of theme performance analysis.
The tool set provides comprehensive coverage for Shopify theme performance profiling: multiple authentication methods, single and batch profiling, raw and summarized output, bottleneck detection, static analysis, comparison, export formats, history tracking, and a health check. No significant gaps are apparent for the stated purpose.