GMC Builder MCP Lite
Related Servers
Alternatives to GMC Builder MCP Lite
No user-submitted related servers found.
Related Servers
- FlicenseBqualityAmaintenanceEnables authenticated, read-only access to configured WordPress or Joomla sites through four MCP tools for site listing, connection checks, page/article listing, and summarizing supplied layout JSON.4-
- AlicenseAqualityAmaintenanceEnables MCP-aware agents to read and explore Oracle Cloud Infrastructure — listing, fetching, and searching across 39 resource types spanning Identity, Compute, Block Volume, Networking, Object Storage, and OKE. Runs locally over stdio using credentials from ~/.oci/config, with fail-closed safety gates and audit logging governing future write operations.4Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP clients such as Codex to safely inspect a MySQL database over stdio by listing tables, describing schemas and indexes, and running only validated single read-only SELECT/CTE queries plus JSON EXPLAIN plans. Queries execute inside read-only transactions with strict AST-based rejection of writes, multi-statements, and other risky operations, and results come back as structured JSON.658 npmMIT
- AlicenseNot gradedqualityBmaintenanceExposes read-only local analysis tools for source auditing, web traffic review, binary reverse engineering, exploit scaffolding, OSINT, and reporting via JSON-RPC over stdio, enabling LLMs to orchestrate evidence-based security workflows without executing targets or sending network requests.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables local, read-only static inspection of Python/FastAPI, Docker, and GitHub Actions release evidence through a stdio interface, returning rule and instance findings without importing or executing target code.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables safe, local DevOps inspection through a JSON-lines server with schema validation, path isolation, and redaction, supporting read-only Git operations, Kubernetes YAML validation, Terraform plan summaries, and sanitized log analysis.MIT
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.