PrestaShop MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRESTASHOP_DOCS_PATH | No | Custom path to the PrestaShop documentation repository. If not set, the server looks for documentation in: 1) ../prestashop-docs (sibling directory), 2) ./prestashop-docs (inside project for Docker builds) |
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_prestashop_hooksB | Search PrestaShop hooks using full-text search. Args: queries: List of search terms (maximum 3) hook_type: Filter by hook type (display, action) origin: Filter by origin (core, module, theme) Returns: Formatted search results with hook details |
| get_prestashop_hookA | Get complete documentation for a specific PrestaShop hook. Args: hook_name: Name of the hook (e.g., 'displayHeader', 'actionProductAdd') Returns: Complete hook documentation including description, parameters, examples |
| list_prestashop_hooksB | List all available PrestaShop hooks. Args: hook_type: Filter by type (display, action) origin: Filter by origin (core, module, theme) Returns: List of all hooks organized by type and origin |
| search_prestashop_docsA | Search ALL PrestaShop documentation (guides, tutorials, API docs, hooks, etc.). Args: query: Search query (e.g., "install", "Mac", "deployment") doc_type: Filter by type: hook, guide, tutorial, api, reference, component, faq, general category: Filter by category: basics, development, modules, themes, etc. Returns: Search results with snippets and metadata |
| get_prestashop_docA | Get the full content of a specific PrestaShop documentation file. Args: path: Document path (e.g., 'basics/installation/environments/macos-specific.md') Returns: Full document content with metadata |
| list_prestashop_docsB | List PrestaShop documentation files. Args: doc_type: Filter by type: hook, guide, tutorial, api, reference, component, faq, general category: Filter by category: basics, development, modules, themes, etc. Returns: List of available documents |
| get_prestashop_statsB | Get statistics about indexed PrestaShop documentation. Returns: Statistics about documents, types, categories, and specialized data |
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
Every tool has a clearly distinct purpose with no overlap: get_doc vs. list_docs vs. search_docs, and similarly for hooks, plus separate stats tool. The descriptions reinforce distinct actions (get, list, search) on different resources (docs, hooks, stats), making misselection unlikely.
All tools follow a consistent verb_noun pattern with 'prestashop' prefix: get_prestashop_doc, list_prestashop_docs, search_prestashop_docs, etc. The naming is predictable and readable throughout, with no deviations in style or convention.
Seven tools is well-scoped for a documentation server, covering core operations (get, list, search) for both docs and hooks, plus a stats tool. Each tool earns its place without feeling thin or bloated, fitting typical MCP server ranges.
The tool surface provides complete coverage for accessing PrestaShop documentation: CRUD-like operations (get, list, search) for both docs and hooks, plus metadata via stats. There are no obvious gaps or dead ends for an agent working with this domain.