customaise
OfficialRelated Servers
Alternatives to customaise
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceConnects AI agents to your Chrome browser via MCP, enabling real-time control of existing tabs, sessions, and application state for development workflows.MIT
- AlicenseNot gradedqualityCmaintenanceLets AI coding agents control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.14 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceLets AI coding assistants control and inspect a live Chrome browser through MCP, enabling reliable automation, debugging, and performance analysis using Chrome DevTools.1,060,392 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceBridges 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.152 npmISC
- AlicenseNot gradedqualityBmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code, Codex, Devin, or any MCP client to control Chrome/Edge through the repository's browser extensions, with Claude-style visual tools or Codex-style text-first tools.5 npmApache 2.0
TDQS
Scored across 19 tools
Most tools target distinct resources or actions, and the descriptions clarify boundaries well. However, import_script and export_script use names that may feel inverted relative to common data-flow conventions, and sync_scripts versus export_script both involve exporting scripts, creating some potential for misselection.
All tools use a consistent snake_case verb_noun pattern (e.g. list_scripts, open_tab, get_page_context, delete_script). There are no mixed conventions or vague standalone verbs.
19 tools is slightly above the typical 3-15 range, but the server covers a broad browser-extension domain including tabs, scripts, WebMCP, context capture, and bridge status. The tools appear well-scoped rather than redundant.
The surface covers script lifecycle (list, import, export/create/update, delete, toggle, sync), tab management, WebMCP tool inspection/calling, page/console context, screenshots, bridge status, and UI toggling. Minor gaps exist, such as directly navigating an existing tab to a new URL, but core workflows are well supported.