Codex Local Ops
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 146 tools
Many tool names have overlapping boundaries: platform_info/platform_capabilities/local_system_info, run_script/job_start/local_shell_run, and every video_*_async duplicates the synchronous video_* operation. Even within browser automation, browser_start/open/navigate could be confused. The large set is organized by domain prefixes, but without descriptions an agent cannot reliably pick between near-synonyms.
Most tools follow lowercase_snake_case with domain prefixes (browser_*, video_*, obs_*, ssh_*), which helps navigation. However verb placement is inconsistent: local_shell_run and job_start are object+verb while run_script and health_check are verb+object, and powershell_run breaks the local_shell_* pattern. The naming is readable but uses mixed conventions.
146 tools is far beyond the 16–25 'heavy' range and into extreme-mismatch territory. Even if the server intentionally spans shell, SSH, WSL, browser, desktop, video, OBS, Docker, and jobs, the sheer number creates major navigation and selection overhead. Most agents would be better served by several smaller focused servers.
The surface covers a wide range of local operations—system info, shell, files, SSH/WSL, browser/desktop automation, video editing, OBS, Docker, git, services, and jobs—so it is far from incomplete overall. Still, several subdomains have gaps (file delete/move, git commit/push, docker compose logs), and the lack of descriptions makes lifecycle coverage hard to verify. These gaps are often workaroundable via shell/job tools, so this is a moderate score rather than a failure.