salla-custom-code-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SALLA_CHROME | No | Path to the Chromium/Chrome executable. Defaults to the Playwright Chromium path. | |
| SALLA_PROFILE | No | Browser profile and backup folder name; useful when using more than one store. | default |
| SALLA_CDP_PORT | No | DevTools port. Use a different port for each store. | 9333 |
| SALLA_STORE_ID | Yes | The allowed Salla store ID (used as a safety check). | |
| SALLA_VERSION_ID | Yes | The default theme version ID. |
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 |
|---|---|
| custom_css_getC | Read the store's custom CSS (theme editor → Advanced customization → CSS) for store 123456789. |
| custom_css_updateA | Replace the store's entire custom CSS. Changes are live on the published version as soon as they are saved. Always read the current CSS first and pass the full new stylesheet (not a fragment). The previous CSS is backed up locally before saving. Show the merchant the change and get their OK before calling. |
| custom_js_getA | Read the store's custom JavaScript for store 123456789. Whether it is enabled is the version's custom_js_enabled flag in the Salla MCP's theme_versions_list. |
| custom_js_updateA | Replace the store's entire custom JavaScript. Runs on every storefront page once saved (if custom JS is enabled). Always read the current JS first and pass the full new script. The previous JS is backed up locally before saving. Show the merchant the change and get their OK before calling. |
| custom_js_toggleA | Turn the store's custom JavaScript on or off without changing the code. Get the merchant's OK first. |
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 5 tools
Each tool targets a clearly distinct resource and action: CSS read/update, JS read/update, and JS enable/disable. There is no meaningful overlap between custom_css_update and custom_js_toggle or any other pair.
All tools follow the same snake_case pattern custom_{css|js}_{get|update|toggle}. The convention is predictable and easy to map to the underlying resources.
Five tools is well-scoped for managing custom CSS and JavaScript. Each tool earns its place by covering a distinct operation without unnecessary surface area.
The surface covers reading and replacing both CSS and JS, plus toggling JS, which is the core workflow. Minor gaps exist around backup/restore visibility or an explicit reset operation, but agents can work around them by passing empty or full content.