GMC Builder MCP Lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GMCBUILDER_MCP_LITE_SITES | Yes | Absolute path to the local sites.json configuration file. Credential environment variables (named by username_env, password_env, and the applicable Joomla token/key field in sites.json) must also be passed to the child process. |
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 |
|---|---|
| gmcbuilder_lite_list_sitesA | List configured site aliases and platform names; never expose credentials. |
| gmcbuilder_lite_ping_siteB | Perform a single authenticated read; return only connection status. |
| gmcbuilder_lite_list_element_typesB | List at most ten builder element type names; no schema or kit export. |
| gmcbuilder_lite_summarize_layoutA | 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 |
|---|---|
| Upgrade to Pro | Show Lite/Pro differences; contains no executable Pro functionality. |
TDQS
Scored across 4 tools
Each tool has a distinct action: enumerating sites, checking one site's connection, enumerating element type names, and summarizing supplied JSON. The only mild overlap is list_sites vs ping_site, both site-scoped, but their descriptions (enumeration vs a single authenticated read returning only status) make the boundary clear.
All four tools follow the same gmcbuilder_lite_verb_noun pattern (list_sites, ping_site, list_element_types, summarize_layout) with consistent snake_case and consistent verb style. No mixed conventions.
Four tools is on the lean side but coherent for an explicitly 'Lite' read-only introspection server; each tool covers a distinct capability. It is slightly thin, with no tool for retrieving a single site's or element type's detail, but nothing is redundant.
The surface covers discovery (sites, element types) and one diagnostic (ping) plus layout summarization, but stops there: there is no way to get details for a specific site or element type, and the descriptions explicitly exclude schema/kit export and layout content. These are deliberate safety limits, yet they leave notable gaps for anything beyond a shallow read.