010 Editor MCP Bridge
Related Servers
Alternatives to 010 Editor MCP Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to search, read, and patch a trusted source repository with rollback-safe edits, Git operations, and allowlisted validation over stdio or OAuth-protected HTTP. Keeps secrets and arbitrary shell access out of reach while enforcing bounded batched I/O and operator-controlled workspace trust.MIT
- AlicenseNot gradedqualityCmaintenanceEnables controlled local Windows file inspection, reading, writing, reversible deletion, restoration, and auditing across user-selected folder roots. Commits occur only after separate owner approval in a native desktop dialog, while the tool cannot bypass OS security controls.MIT
- FlicenseAqualityAmaintenanceEnables coding agents to perform workspace-confined file operations, read-only Git inspection, and structured shell commands, while requiring out-of-band human approval for mutations and external executions and maintaining an audit trail.143-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to safely explore directories, read files, search content by pattern or filename, and edit files with checksum verification and dry-run preview within sandboxed filesystem access.15 npm75ISC
- AlicenseAqualityBmaintenanceEnables coding agents to safely inspect and modify project files within explicitly allowed workspace roots, with controls for file operations, git status/diff, and optionally allowlisted command execution.11Apache 2.0
- AlicenseAqualityCmaintenanceEnables read-only binary diff and fingerprinting of files without writing to disk, providing structured diffs and per-section SHA-256 hashes.3MIT
TDQS
Scored across 14 tools
Clear split between binary_* disk operations and editor_* live-buffer operations, with each tool targeting a distinct action. Minor potential confusion between binary_read and binary_inspect, and between server_status and editor_status, but descriptions sufficiently distinguish them.
All tools use snake_case with a consistent domain_verb_noun naming pattern (binary_* / editor_*). The single server_status is a reasonable global exception and does not break readability.
14 tools is within a reasonable range for a bridge covering disk and live-editor operations, but including editor_patch_apply as a CAPABILITY_UNSUPPORTED placeholder and the unusable editor_patch_preview/apply pair means a couple of tools do not earn their place.
Disk-side coverage is decent (read, search, diff, inspect, patch preview/apply), but the live editor surface has a major gap: no atomic unsaved-buffer write is available, and editor_patch_apply is explicitly disabled. This leaves editor mutation workflows incomplete.