010editor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDITOR010_EXE | No | Override the 010 Editor binary with the full path to 010Editor.exe / 010editor. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| editor_statusA | Report whether 010 Editor is installed and which binary would be used. Override discovery with env EDITOR010_EXE (full path to 010Editor.exe / 010editor). Also accepts ZERO10_EXE or 010EDITOR_EXE. |
| run_templateB | Run a Binary Template (.bt) on a data file via 010 Editor CLI. Uses: 010editor -template:.bt -noui -nowarnings -<exit_mode> Working directory is the template's parent folder so -template: resolves. |
| run_scriptB | Run a 010 Editor Script (.1sc), optionally on a data file. Uses: 010editor [data] -script:.1sc -noui -nowarnings -<exit_mode> Cwd is the script's parent directory. Scripts can call RunTemplate("foo.bt") and Exit(n) for custom codes. |
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 3 tools
The three tools have clearly distinct purposes: checking editor availability, running a Binary Template, and running a 010 Editor Script. There is no meaningful overlap between status reporting and execution.
Names are consistently snake_case and mostly follow verb_noun (run_template, run_script). editor_status is a noun phrase rather than a verb, a minor deviation but still clear and predictable.
Three tools is well-scoped for a focused CLI wrapper around 010 Editor. Each tool earns its place and there is no redundancy.
The surface covers the core lifecycle: verify installation, run templates, and run scripts. Minor gaps exist around discovering available templates/scripts or structured output handling, but agents can work around these via paths and script exit codes.