Skip to main content
Glama
gmcfuerte

GMC Builder MCP Lite

by gmcfuerte
README.md
# GMC Builder MCP Lite

Free limited companion to the GMC Pro product. This is a separate **0.1.3**
client with a fresh history and only four read-only MCP tools. The Pro
implementation is absent from this repository.

[![Listed on mcpservers.org](https://mcpservers.org/badge.svg)](https://mcpservers.org/servers/gmcfuerte/gmcbuilder-mcp-lite)

[![Listed on AllMCPs](https://allmcps.com/api/badge/gmc-builder-mcp-lite)](https://allmcps.com/mcp/gmc-builder-mcp-lite?verify=8e394cba-4695-474c-8797-17f853d501bc)


## Lite and Pro

| Capability | Lite | Pro product |
| --- | --- | --- |
| Configured site aliases | Yes | Yes |
| Authenticated connection probe | Yes | Yes |
| Up to 10 element types per call | Yes | Extended tools |
| Local supplied JSON: node counts/types | Yes, input up to 64 KiB | Detailed inspection |
| Create/edit/publish layouts or documents | No | Paid functionality |
| Full export/import, bulk editing, backups | No | Paid functionality |
| Private Pro implementation or CMS companion source | Absent | Separately distributed |

See [Pro features and current annual plans](https://fuerteventuratv.net/en/cms/gmcbuilder-mcp). Contact **gmcfuerte@gmail.com** for companion requirements or product questions.

Lite is free to use under the [limited commercial licence](LICENSE).
Source visibility does not grant redistribution or resale rights.

## Upgrade to Pro in your MCP client

Open the resource **Upgrade to Pro** (`gmc://lite/pro-features`) to see the
capability comparison and the product's current plans. Editing, publishing,
full import/export, bulk editing and restoration are labelled **unavailable
in Lite**. They are informational previews; no Pro code or executable Pro
tools are bundled. The free tools keep working without an upgrade.

MCP clients decide how resources are displayed, so this is not a guaranteed
popup or a graphical settings panel. Ask your assistant to read the resource
if its client does not expose a resource browser.

## Guide and presentation

- [Practical Lite guide (English)](https://fuerteventuratv.net/en/joomla-app/1887-gmc-mcp-lite-practical-guide): prerequisites, setup and a first read-only session.
- [Presentation for clients (Italian PDF)](https://fuerteventuratv.net/images/manuali-cms/GMC-MCP-presentazione-clienti-IT-20261012.pdf): a short overview of the three Lite clients and the separate Pro editions.
- [Pro features and annual plans](https://fuerteventuratv.net/en/cms/gmcbuilder-mcp).

## Prerequisites

Python 3.10 or newer. GMC Builder installed on the target site: WordPress authoring API (2.0.0+) with an Application Password, or Joomla remote API (2.0.1+) with the shared X-Gmc-Builder-Key. This repository does not distribute GMC Builder. Obtain the CMS product through GMC; no layout-export endpoint is included in Lite.

## Install from GitHub

```console
git clone https://github.com/gmcfuerte/gmcbuilder-mcp-lite.git
cd gmcbuilder-mcp-lite
python -m venv .venv
```

Windows:

```console
.venv\Scripts\python.exe -m pip install .
```

macOS/Linux:

```console
.venv/bin/python -m pip install .
```

This Lite edition is distributed through this GitHub repository; it has
not been published to PyPI. Do not install the separate full Pro package
as a substitute for Lite.

## Configure

1. Copy `sites.example.json` to a **local** `sites.json` and keep only the
   sites you own or are authorized to access. The file is ignored by Git.
2. Set the credential environment variables named by `username_env`,
   `password_env`, and the applicable Joomla token/key field. Never put
   credential values in committed JSON or an MCP chat.
3. Set `GMCBUILDER_MCP_LITE_SITES` to the absolute path of that local JSON file.
4. Add the server using `mcp.example.json`: replace the placeholders with
   the absolute Python executable and configuration file paths. Ensure
   the MCP client passes the credential variables to its child process.
5. Start with `gmcbuilder_lite_list_sites`, then `gmcbuilder_lite_ping_site`.

`rest_mode: "query"` supports WordPress without pretty REST URLs; otherwise
use `pretty`. Subdirectory installations are supported in the base URL.

## Tools

- `gmcbuilder_lite_list_sites`: aliases and platforms only.
- `gmcbuilder_lite_ping_site`: one authenticated GET, sanitized status only.
- `gmcbuilder_lite_list_element_types`: List at most ten builder element type names; no schema or kit export.
- `gmcbuilder_lite_summarize_layout`: pass the text from `layout.example.json`
  as `layout_json`. Returns counts and types; no settings or content.

The server runs locally using **stdio**. No remote HTTP server, uploads,
arbitrary URLs, SSH, license switch or Pro modules are included. Online
tools use a fixed GET allowlist, verified TLS, no redirects, at most one
request at a time per configured base URL, a two-second interval, and a
1 MiB response limit. HTTP is accepted only for exact loopback hosts.
HTTP 403/415 stops subsequent requests to that base URL until restart.

## Release status

Initial Lite release: source and package contents inspected and Python
compiled. Site integration and runtime tests have not been performed.
Do not treat this initial release as a production integration certification.

## Contact

[GMC](https://fuerteventuratv.net/en/cms) · gmcfuerte@gmail.com.
Independent GMC software; product names belong to their respective owners.

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues