# qodercli-mcp [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/cantbeblank96/qodercli-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 206  
**Views:** 7  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/qodercli-mcp

## Description
MCP server mode for Qoder CLI — delegate coding tasks to local Qoder agents from any MCP client.

## Tools
Capabilities this server exposes over MCP:

- **ask-qoder** — Delegate a task to qodercli (Qoder CLI), a local agentic coding assistant. Use it to get a second opinion, a code review, or to have Qoder perform a self-contained coding task in a given working directory. Returns structured output including session_id; pass it back as resume_session_id to continue the conversation.
- **list-sessions** — List local qodercli sessions (index + id + summary) so you can pick a resume_session_id for ask-qoder.
- **list-models** — List models currently supported by qodercli. Use this before picking a model name for ask-qoder.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "qodercli-mcp": {
    "command": "npx",
    "args": ["-y","qodercli-mcp"]
  }
}
```

## Documentation

## What qodercli-mcp MCP server does

The qodercli-mcp MCP server connects MCP clients to the locally installed Qoder CLI. Rather than implementing an agent itself, it acts as a wrapper around qodercli and exposes Qoder's local execution through MCP tools. This lets a connected client send coding tasks, questions, and review requests to a Qoder agent running on the same machine.

The main entry point is `ask-qoder`. It accepts a prompt and optional execution settings such as the working directory, model, reasoning effort, system prompt, output format, and timeout. A returned session ID can be used to continue a previous delegation. Results include human-readable content and structured execution details when JSON output is used.

## How it works

The qodercli-mcp MCP server launches `qodercli -p <prompt>` as a child process and communicates with the MCP client over standard input and output. The wrapper parses qodercli JSON output and exposes fields including the session ID, error state, exit code, duration, credit usage, turn count, timeout state, and truncation state.

Its permission controls map MCP arguments to Qoder CLI behavior. The default `dont_ask` mode is read-only and silently denies permission-requiring actions. `workspace-write` allows file changes in the selected working directory, while `danger-full-access` permits full access including shell operations. Explicit `permission_mode` or `approval_policy` settings take precedence over `sandbox`.

Two read-only discovery tools complement task delegation. `list-sessions` returns local sessions that can be resumed, and `list-models` queries qodercli at runtime for currently supported model names.

## Setup and configuration

Node.js 18 or newer and an installed, signed-in `qodercli` are required. The published package can be started with `npx -y qodercli-mcp`, so an MCP client can download it on first use. A source checkout can instead run the package's `src/index.js` with Node after `npm install`.

Add the server to the MCP client's configuration with a `command` and `args` entry. Set `QODERCLI_PATH` when the executable is not visible to the child process, which is especially relevant for installations managed by nvm. A local checkout may also need an absolute Node path. `HTTP_PROXY` and `HTTPS_PROXY` can be supplied when qodercli should use a proxy quota.

## Tools and capabilities

- `ask-qoder`: delegates a prompt and supports working directories, models, reasoning effort, prompts, session resume, permission settings, raw safe CLI arguments, output format, and timeouts.
- `list-sessions`: lists local resumable qodercli sessions without arguments.
- `list-models`: discovers available models at runtime and returns both text and structured model data.
- Structured output: reports execution metadata through MCP `structuredContent` when JSON output is used.
- Timeout handling: stops long-running processes and has a SIGKILL fallback.

## Limitations and notes

The qodercli-mcp MCP server depends on the local Qoder CLI, its sign-in state, and the models available to that installation. It does not provide an independent model catalog. Non-JSON output formats reduce the structured metadata available from `ask-qoder`.

The `default` permission mode expects interactive confirmation and is not suitable for headless MCP calls. Read-only behavior is the default, but selecting write or full-access modes changes what the delegated agent can do in the configured working directory or system. Raw `extra_args` are restricted: reserved flags for permissions, prompts, models, output, resume, and working directory are rejected.

_Full upstream README: https://allmcps.com/mcp/qodercli-mcp/readme_