A
licenseA
qualityD
maintenanceEnables LLMs to interact with MIT App Inventor, AndroidBuilder, Kodular, or Niotron IDEs in real-time, controlling the Designer and Blocks workspace via Chrome DevTools Protocol.
10
MIT
cyberbrick-mcp
by jarvisluk
Related Servers
Alternatives to cyberbrick-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables agents to inspect and drive Electron or Chrome/Chromium apps via the Chrome DevTools Protocol, exposing DOM snapshots, console logs, network requests, and gated interactions like clicking, typing, and navigating.6252 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables the Pi coding agent to drive Chrome through DevTools, providing browser automation tools, persistent or isolated profiles, screenshots, page analysis, and bundled agent policies.05MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to perform bounded browser tasks by discovering or connecting to local Chromium/Electron endpoints, inspecting pages, and executing grounded page actions or Chrome DevTools operations.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control and inspect a live Chrome browser via MCP, providing Chrome DevTools capabilities for automation, debugging, and performance analysis.2,848,483 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to drive a logged-in ChatGPT web session over CDP, including managing projects and chats, sending messages with file attachments, and retrieving long Pro replies.124MIT
TDQS
B3.3/5.0
Scored across 41 tools
Disambiguation4/5
Most tools have clearly distinct purposes, with explicit warnings for destructive and mutating operations. Some overlap exists among device inspection tools (device_detail vs. board_info vs. device_status) and firmware/config editing paths (firmware_config_set vs. firmware_config_edit vs. project_save), but the descriptions generally clarify boundaries.
Naming Consistency3/5
All names use snake_case, but the structural conventions are mixed: some tools are resource_action (project_rename, device_list), others action_resource (flash_mpy, connect_bluetooth), and some have unique prefixes (cb_health, app_logs, board_info). The grouping is readable, but there is no single predictable naming pattern.
Tool Count2/5
At 41 tools, the surface is very heavy for an MCP server, even for a complex app-plus-hardware integration. Several tools are specialized or low-level, and the count exceeds the typical comfortable range without strong evidence that all are required for common agent workflows.
Completeness4/5
The tool set covers the domain broadly: project lifecycle, firmware config editing, device inspection, BLE/serial connection, flashing, health checks, logs, and window management. Minor gaps exist, such as explicit disconnect/unpair operations and higher-level device session cleanup, but core workflows are well supported.
Maintenance
ActivityMaintained
ResponsivenessNo issues