Skip to main content
Glama
getcustomaise

customaise

Official
by getcustomaise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to customaise

No user-submitted related servers found.

    Related Servers

    • Tabryn

      idugeni
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects AI agents to your Chrome browser via MCP, enabling real-time control of existing tabs, sessions, and application state for development workflows.
      MIT

    • LoopIn

      skip5this
      A
      license
      Not graded
      quality
      D
      maintenance
      Bridges a browser extension with an AI agent via MCP, enabling the agent to capture and act on UI elements, styles, and accessibility data from web pages.
      153 npm
      ISC

    • browserpilot-mcp

      Fire162
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables remote AI agents to control a local, authenticated desktop browser over MCP through an outbound WebSocket bridge and Chrome extension, supporting tab management, navigation, page reading, clicking, typing, scrolling, screenshots, and JavaScript evaluation.
      1
      MIT

    • VSCode Automation MCP

      Sukarth
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to programmatically control and automate VSCode by interacting with its UI, executing commands, and inspecting the DOM structure. It supports advanced workflows like UI testing, extension development, and debugging through a standalone VSCode instance.
      5 npm
      8
      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

    A4.1/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have distinct purposes (script lifecycle vs browser tab control vs context inspection), but get_page_context, get_selected_elements, and get_console_context all provide page/browser context and could be confused by an agent deciding which one to call. The descriptions are detailed enough to mostly disambiguate, but the overlap in 'get context' naming creates some ambiguity.

    Naming Consistency4/5

    The naming is predominantly verb_noun (export_script, import_script, list_scripts, delete_script, toggle_script, open_tab, close_tab, reload_tab, focus_tab, list_tabs, take_screenshot, get_bridge_status, get_page_context, get_console_context, get_selected_elements). Minor deviations: call_webmcp_tool and list_webmcp_tools use a different verb style, and sync_scripts is a verb_noun but with a different verb. Overall consistent and predictable.

    Tool Count4/5

    19 tools is on the higher end but appropriate for a server that covers both script management and browser automation. Each tool serves a distinct function, though a few could be consolidated (e.g., context getters). The count is justified by the dual domain (Customaise scripts + browser tab control).

    Completeness4/5

    The script lifecycle is well covered: list, import, export, delete, toggle, sync. Browser tab control is covered: open, close, focus, reload, list, screenshot. Missing operations include script publishing/sharing and direct script execution control, but the core workflows (edit scripts, test on pages, manage tabs) are complete. The bridge status and WebMCP tool listing fill important gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources