Developer · Local MCP server
Qodercli MCP
MCP server mode for Qoder CLI - delegate coding tasks to local Qoder agents from any MCP client.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.cantbeblank96/qodercli-mcp- Version
- 0.4.3
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-08-20
- Updated
- 2026-08-20
- Publisher
- cantbeblank96 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/cantbeblank96) · how
- Repository
- github.com/cantbeblank96/qodercli-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | qodercli-mcp | 0.4.3 | stdio |
How to connect Qodercli MCP
Qodercli MCP runs locally from a Node.js package published to the npm registry: qodercli-mcp version 0.4.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y qodercli-mcp@0.4.3. It reads these environment variables: QODERCLI_PATH, QODERCLI_DEFAULT_PERMISSION_MODE, HTTP_PROXY and HTTPS_PROXY; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"qodercli-mcp": {
"command": "npx",
"args": [
"-y",
"qodercli-mcp@0.4.3"
],
"env": {
"QODERCLI_PATH": "<value>",
"QODERCLI_DEFAULT_PERMISSION_MODE": "<value>",
"HTTP_PROXY": "<value>",
"HTTPS_PROXY": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| qiklyGenerates tests from acceptance criteria, then converges code with an agent that never sees them. | Local · stdio |
| QlaneAI QA that runs your app in a browser on every pull request: projects, test targets, test cases. | Remote · HTTPLive check: sign-in required |
| qmailing.comAI agents read & send email, manage mailboxes, domains and webhooks via the QMailing API. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Qnexus MCPMCP server for Quantinuum Nexus, wrapping the qnexus SDK. Not affiliated with Quantinuum. | Local · stdio |
| Qovery MCP ServerDeploy apps and manage Kubernetes on AWS, GCP, Azure, and On-Premise with natural language. | Remote · HTTP |
| QR for AgentDynamic QR codes for AI agents - custom styling, scan tracking, webhooks. | Local · stdio |
| qrvoteQR-code contests, surveys, quizzes and scavenger hunts: read results, manage your own. | Remote · HTTPLive check: ✓ handshake |
| Qsp ClientQSP - relay MCP tools to any OpenAI-compatible local LLM (llama.cpp, Ollama, vLLM) | Local · stdio |