Skip to main content
Glama
tcgunel

mobius-studio-mcp

by tcgunel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mobius-studio-mcp

No user-submitted related servers found.

    Related Servers

    • wp-mcp-server

      eimon
      A
      license
      A
      quality
      C
      maintenance
      Enables an AI design agent to connect to any WordPress site, inspect its real rendered CSS/JS/theme, and create or update pages through the WordPress REST API and optional companion plugin routes.
      6
      7 npm
      MIT

    • wp-mcp

      Adi-ty
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects WordPress sites to AI agents, enabling content management through natural language commands via the WordPress REST API.
      11 npm
      2
      MIT

    • WordPress MCP Server

      wolffcatskyy
      A
      license
      Not graded
      quality
      F
      maintenance
      Enables AI models like Claude to manage WordPress sites through the WordPress REST API, supporting operations like post creation, taxonomy management, and site configuration. It features secure authentication via Application Passwords and provides tools for comprehensive content administration.
      62 npm
      1
      MIT

    • WordPress MCP Server

      gaupoit
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage WordPress sites through natural conversation, supporting post creation, content updates, site queries, and draft-to-publish workflows via the WordPress REST API.
      9
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct actions or resources: status checks, demo import, AI planning, and brief copy are clearly separated. A few boundaries could still trip an agent, such as sweipe_status vs sweipe_import_status or sweipe_list_demos vs sweipe_ai_library, but the descriptions provide enough to disambiguate.

    Naming Consistency4/5

    The names consistently use snake_case and a sweipe_ prefix, with wp_ used for the WordPress core tools. There are minor structural deviations like sweipe_site_from_brief and sweipe_brief_pages where the noun/phrase form replaces the usual verb_noun pattern, but the overall scheme is predictable.

    Tool Count3/5

    Twenty tools is on the heavy side for a single server, and the 16-25 range makes it feel sprawling. That said, the functions are grouped into distinct workflows (demos, AI site building, brief copy), so the count is defensible even if it could be consolidated.

    Completeness4/5

    The server covers the full Sweipe lifecycle: licensing/status, demo import, AI plan/build/review, one-shot brief-to-site, and the copy brief workflow with undo. Minor gaps exist, such as no direct arbitrary page editing or delete/cancel operations, but the core workflows are complete and have no dead ends.

    Resources