local-agent-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_DEBUG | No | When true, full prompts are written to the stderr debug log. | false |
| AGENT_ALLOW_WRITE | No | When true, permits codex_run workspace_write and opencode_run auto_approve. | false |
| AGENT_ALLOWED_ROOTS | Yes | Comma-separated absolute directories agents may access. | |
| AGENT_MAX_CONCURRENCY | No | Max simultaneous agent runs. | 3 |
| AGENT_MAX_OUTPUT_BYTES | No | Max combined stdout+stderr bytes captured per run. | 5000000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agent_healthA | Report the local agent environment: Node version, Git availability, Codex/OpenCode install status and versions, allowed working directories, whether writes are permitted, and current concurrency usage. |
| codex_runA | Run the locally installed, logged-in Codex CLI non-interactively in a sandboxed working directory. Defaults to read-only. Use workspace_write only when writes are enabled server-side. Returns the final agent message plus command/file-change/error summaries. |
| opencode_runA | Run the locally installed, logged-in OpenCode CLI non-interactively in a sandboxed working directory. auto_approve enables side-effecting actions and requires server-side write permission. Supports session continuation and agent/model selection. |
| agent_compareA | Run Codex and OpenCode against the same prompt in READ-ONLY mode and return both results verbatim. Does not judge which is better; the caller synthesizes the conclusion. One agent failing does not suppress the other. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/3230390742/local-agent-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server