YOOtheme MCP Lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YOOTHEME_MCP_LITE_SITES | Yes | Absolute path to the local sites.json configuration file. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yootheme_lite_list_sitesA | List configured site aliases and platform names; never expose credentials. |
| yootheme_lite_ping_siteC | Perform a single authenticated read; return only connection status. |
| yootheme_lite_list_pagesB | List at most ten page/article titles, ids and status; no content export. |
| yootheme_lite_summarize_layoutB | Summarize supplied JSON node types; never return layout content or settings. |
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 4 tools
Each tool targets a distinct action and resource: listing sites, pinging a site, listing pages, and summarizing layout JSON. No two tools overlap in purpose, and the descriptions clearly delineate their boundaries.
All tool names follow the same yootheme_lite_ prefix and snake_case verb_noun pattern (list_sites, ping_site, list_pages, summarize_layout). This consistency makes them predictable and easy to select.
Four tools are appropriate for a 'lite' server focused on safe, read-only introspection. Each tool earns its place without redundancy, and the count is well within the typical 3–15 range.
The surface covers listing and basic checks but lacks get operations for individual sites, pages, or layouts, and has no write or update capabilities. While intentional for a lite server, these gaps limit deeper inspection and may force agents to seek other tools.