Skip to main content
Glama
Sign In
LightCMS

LightCMS

by metavert-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Related Servers

Alternatives to LightCMS

No user-submitted related servers found.

    Related Servers

    • mini-cms-mcp

      paycodero
      A
      license
      A
      quality
      B
      maintenance
      Small self-hosted CMS (PHP 8, no database) for sites with a few pages and a blog, managed by an AI assistant over MCP. The AI changes content, never code: pages, posts, menus, images, PDF documents, redirects, drafts and version history.
      26
      MIT

    • content-hub

      X33834
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to manage a self-hosted content hub: create, edit, publish, and update articles across multiple platforms, plus AI writing and account management.
      2
      MIT
    • RedStudio MCP

      RedStudio MCPofficial

      REDStudioOrg
      A
      license
      A
      quality
      C
      maintenance
      Lets AI assistants publish and edit pages, components, media and blog posts on a hosted RedStudio website, with shop, Stripe payments, bookings and event tickets included. Site settings, redirects, booking hours and revisions are all managed through the assistant instead of a separate backend.
      29
      24 npm
      MIT

    • sitemd

      sitemd-cc
      A
      license
      Not graded
      quality
      F
      maintenance
      Static site generator / website building toolkit for AI coding agents like Claude, Codex, Cursor, Gemini, OpenClaw, etc. No subscription, no lock-in — host your site anywhere.
      12 npm
      9
      Elastic 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 129 tools

    Disambiguation3/5

    Most tools target clearly distinct resources, but several clusters create real ambiguity: the fork tools (create_fork/fork_page/merge_fork) vs the sandbox tools (start_agent_sandbox/end_agent_sandbox) describe the same underlying mechanism, search_replace_execute vs scoped_search_replace_execute vs preview variants overlap, and update_content vs update_content_by_path vs bulk_update_content compete for the same job. Detailed descriptions help, but an agent still has to reason carefully about which of several near-duplicates to pick.

    Naming Consistency4/5

    Names overwhelmingly follow a predictable verb_noun snake_case pattern (list_content, get_content, create_content, update_content, delete_content), with parallel families for templates, folders, collections, snippets, redirects, webhooks, and approvals. Minor deviations exist — get_theme_version (singular) alongside get_theme_versions, force_unlock_content vs acquire/release_content_lock, and import_csv/import_markdown — but they remain readable and semantically consistent.

    Tool Count2/5

    129 tools is excessive even for a broad CMS domain, far past the 50+ 'extreme mismatch' threshold. Many operations could be consolidated (e.g., separate lock get/acquire/release/force, singular/plural version getters, three publish paths), so each tool does not clearly earn its place.

    Completeness5/5

    The surface is remarkably complete: full content CRUD plus versions, soft-delete/restore, drafts/publish/scheduling, locks, comments, templates/fields, folders, collections, snippets, themes with versioning, assets, webhooks, redirects, imports, approval workflows, forks/sandbox staging, SEO/IndexNow, maintenance scans, and audit logs. Almost no lifecycle gap is left uncovered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources