Skip to main content
Glama
ToolsEnabled

Site Studio

by ToolsEnabled
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Site Studio

No user-submitted related servers found.

    Related Servers

    • Sophia Stack MCP

      Chorozion
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables external AI agents to edit and manage a self-hosted website via a token-gated MCP server, including page content, data, media, and sandboxed functions with validation and rollback.
      3
      Apache 2.0
    • SitePerto MCP by Store-Experts

      SitePerto MCPofficial

      Store-Experts
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to connect to a selected website via OAuth, send ready-to-use static HTML packages, read and edit text, CSS, and JavaScript with preview, and manage pending updates without automatic publishing.
      3
      1
      MIT

    • pages-mcp

      RobertDWhite
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables uploading and serving static websites via MCP tools, with automatic path prefix injection for multi-file sites.
      -

    • Gutenberg's Hoard

      Luissalet
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables local publication cataloguing, persistent native DesignCraft editing sessions, page workspace operations, source linking via hoard:// references, preview rendering, and verified multipage RGB-raster PDF export through MCP tools.
      -
    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.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, but web_read, web_pages, web_find, and web_css all involve reading related content, and web_screenshot_note/web_preview both return revision info. Descriptions help clarify boundaries, though some overlap remains.

    Naming Consistency3/5

    All tools share a 'web_' prefix, but conventions are mixed: some are verbs (web_read, web_find), some are nouns (web_pages, web_css, web_timeline), and some are verb_noun (web_set_text, web_add_page). The inconsistent ordering of web_css_set further breaks the pattern.

    Tool Count4/5

    16 tools is slightly above the ideal 3-15 range, but the domain is rich (reading, writing, CSS, SVG, checkpoints, preview). Each tool appears to earn its place, so the count is reasonable if a bit heavy.

    Completeness3/5

    Core CRUD for nodes and attributes is covered, but several lifecycle operations are missing or only available via the dashboard: undo/redo/restore, checkpoint restore/delete, file-level deletion, and CSS file creation. Agents can work around some gaps, but these are notable omissions for a revision-based editor.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources