Shopify Liquid MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHOPIFY_LIQUID_DB_PATH | No | Custom database location for the Shopify Liquid documentation database |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_liquid_docsB | Search Shopify Liquid documentation using full-text search. Args: queries: List of search terms (maximum 3) Returns: Formatted search results with snippets |
| get_liquid_tagA | Get documentation for a specific Shopify Liquid tag. Args: tag_name: Name of the tag (e.g., 'if', 'for', 'assign') Returns: Complete tag documentation |
| get_liquid_filterA | Get documentation for a specific Shopify Liquid filter. Args: filter_name: Name of the filter (e.g., 'upcase', 'date', 'money') Returns: Complete filter documentation |
| get_liquid_objectB | Get documentation for a specific Shopify Liquid object. Args: object_name: Name of the object (e.g., 'product', 'cart', 'shop') Returns: Complete object documentation |
| list_liquid_tagsA | List all available Shopify Liquid tags. Returns: List of all tag names with titles |
| list_liquid_filtersA | List all available Shopify Liquid filters. Returns: List of all filter names with titles organized by category |
| list_liquid_objectsB | List all available Shopify Liquid objects. Returns: List of all object names with titles organized by category |
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 7 tools
Each tool has a clearly distinct purpose with no ambiguity: three 'get' tools retrieve specific documentation for filters, objects, and tags respectively; three 'list' tools enumerate all available items in those categories; and one 'search' tool performs full-text queries. The boundaries between tools are well-defined, preventing misselection.
Tool names follow a highly consistent verb_noun pattern throughout: all start with 'get_', 'list_', or 'search_' followed by 'liquid_' and the specific resource type (filter, object, tag, docs). There are no deviations in style or convention, making the set predictable and readable.
With 7 tools, the count is well-scoped for the server's purpose of providing Shopify Liquid documentation. It covers key operations (retrieve specific items, list all items, search) across the main documentation categories (filters, objects, tags), with each tool earning its place without redundancy or bloat.
The tool surface is complete for the domain of Shopify Liquid documentation lookup. It offers full CRUD-like coverage: 'list' tools for discovery, 'get' tools for detailed retrieval, and a 'search' tool for flexible queries. There are no obvious gaps or dead ends, enabling agents to handle all typical documentation needs effectively.