DevBridge MCP
Related Servers
Alternatives to DevBridge MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Codex to launch and orchestrate local agent sessions, delegate tasks, return clickable live web links, and independently verify actual workspace changes.126 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables ChatGPT to securely inspect local Codex projects, read session history, and dispatch confirmed tasks to the Codex CLI through a local MCP bridge.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to safely read, search, understand, and edit local project code and files, with Git inspection, code indexing, and controlled command execution within permissioned workspaces.8 npm6MIT
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to inspect and edit local projects, run bounded commands and Git operations, control Chrome or Edge, manage connected Excel workbooks, and explicitly call Codex when model work is actually needed.MIT
- FlicenseNot gradedqualityAmaintenanceEnables ChatGPT to inspect and edit local projects, run bounded commands, use Git, automate Chrome or Edge, and control connected Excel workbooks, while invoking the Codex model only when explicitly needed.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely inspect, modify, and manage local projects with trusted filesystem access, safe Git operations, controlled task execution, and developer runtime process management over stdio or HTTP.4Apache 2.0
TDQS
Scored across 40 tools
Tools are grouped into clear sub-domains (Codex history, filesystem, browser, terminal/tasks, design, integrations) and names mostly specify both resource and action, so most selections are unambiguous. A few boundaries blur: design_profiles vs design_library_catalog and browser_snapshot vs browser_source_probe vs browser_diagnostics require reading descriptions to differentiate, and design_library_guidance overlaps conceptually with design_audit.
Dominant convention is snake_case verb_noun (read_file, patch_file, search_files, browser_click, design_initialize), with consistent prefixes per sub-domain (browser_, design_, design_library_, terminal_, project_task_). Minor deviations are noun-first names such as file_info, browser_status, codex_storage_info, and integration_catalog, which break the pattern without harming readability.
40 tools is heavy for a single server, and the surface spans at least eight loosely related domains (history indexing, filesystem, Playwright automation, command execution, design references, static analysis, docs). While each tool is non-redundant, the volume forces agents to sift a large catalog and suggests the server should be split by concern.
Each sub-domain has near-full lifecycle coverage: plan/run pairs for terminal and project tasks, scan/search/get/list for Codex history, and open/snapshot/click/fill/diagnostics/close for the browser, plus a coherent design-reference workflow (catalog, read, import, initialize, audit, guidance). Gaps exist—no delete/rename/move for files, no mkdir, and git is inspect-only—but these appear deliberate (allowlist safety) and are workable around.