010 Editor MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_statusA | Report backend availability, configured limits and local path boundaries. |
| editor_statusA | Detect an existing editor/bridge and report supported live capabilities. |
| binary_inspectB | Inspect an allowed ordinary disk file, optionally streaming requested hashes. |
| binary_readA | Read bounded bytes from disk by zero-based byte offset; never read an editor buffer. |
| binary_searchC | Search a bounded disk interval for hex bytes, including overlapping matches. |
| binary_diffC | Compare bounded disk-file intervals and return precise bounded difference ranges. |
| binary_patch_previewB | Verify disk bytes and preview replacement; retain its token for a copy-on-write apply. |
| binary_patch_applyB | Apply a previewed disk replacement to a new output file; preserve the original. |
| editor_contextA | Read active buffer identity, dirty state and selection without changing selection. |
| editor_readB | Read the intended live in-memory buffer, including unsaved bytes; no disk fallback. |
| editor_selectB | Select/navigate to a zero-based byte range in the explicitly identified live buffer. |
| editor_run_templateC | Run a .bt template from a configured trusted root on the intended live buffer. |
| editor_patch_previewC | Verify and preview live bytes; can_apply is false and no mutation token is issued. |
| editor_patch_applyC | Report CAPABILITY_UNSUPPORTED: atomic unsaved-buffer writes are disabled this release. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.