Qoder CN CLI MCP servers,stdio,sse,http,ws,permissions,troubleshooting -

Qoder CN CLI can connect to Model Context Protocol (MCP) servers to access external tools and data sources. Once a server is added, its tools become available to the agent in both interactive and non-interactive sessions.

Quick start

Use qoderclicn mcp add to add a stdio MCP server. The command after -- is the server process that Qoder CN CLI will start.

qoderclicn mcp add playwright -- npx -y @playwright/mcp@latest

Stdio servers start automatically with the CLI. If Qoder CN CLI is already running, use /mcp reload to rediscover MCP servers and tools; new sessions discover them automatically on startup.

Server types

Use -t to select the MCP transport type.

Type	Use case
`stdio`	The MCP server runs as a local command
`sse`	The MCP server is exposed via a Server-Sent Events endpoint
`http`	The MCP server is exposed via an HTTP endpoint
`ws`	The MCP server is exposed via a WebSocket endpoint

If no type is specified, local command servers use the default stdio behavior.

Scopes

Use -s to select where the MCP server configuration is saved.

Scope	Use case
`user`	Make the server available across all projects for the current user
`local`	Make the server available only in the current project on this machine. This is the default scope (`local`)
`project`	Share the server configuration with the project

MCP server configurations are stored in the following files:

# User-level configuration.
~/.qoder-cn/settings.json

# Local project-level configuration. Typically not committed.
${project}/.qoder/settings.local.json

# Project-level configuration. Typically committed with the project.
${project}/.mcp.json

Manage servers

List configured servers:

qoderclicn mcp list

Remove a server:

qoderclicn mcp remove playwright

Common MCP servers include:

qoderclicn mcp add context7 -- npx -y @upstash/context7-mcp@latest
qoderclicn mcp add deepwiki -- npx -y mcp-deepwiki@latest
qoderclicn mcp add chrome-devtools -- npx chrome-devtools-mcp@latest

Permissions

MCP tools still go through the Qoder CN CLI permission system. In the default mode, calling an MCP tool typically prompts for confirmation. You can approve a specific tool, approve all tools from an MCP server, or configure rules in settings.

MCP tool names typically follow this format:

mcp__<server>__<tool>

Example:

{
  "permissions": {
    "allow": [
      "mcp__context7__*"
    ],
    "deny": []
  }
}

Troubleshooting

If MCP tools are unavailable:

Run qoderclicn mcp list to confirm the server is configured.
If Qoder CN CLI is already running, run /mcp reload after adding or modifying a server.
Verify that the command after -- runs successfully in a terminal.
For npx-based servers, confirm that Node.js and network access are available.
If the server is connected but tool calls are blocked, check the permission prompt.