Qwen3-Coder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLLAMA_KEEP_ALIVE | No | Keep models loaded for 24 hours | 24h |
| OLLAMA_NUM_PARALLEL | No | Handle parallel requests | 8 |
| OLLAMA_KV_CACHE_TYPE | No | High-quality 8-bit cache | q8_0 |
| OLLAMA_FLASH_ATTENTION | No | Enable efficient attention mechanism | 1 |
| OLLAMA_MAX_LOADED_MODELS | No | Keep models in memory simultaneously | 4 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qwen3_code_reviewC | Review code using Qwen3-Coder |
| qwen3_code_explainC | Explain code using Qwen3-Coder |
| qwen3_code_generateC | Generate code using Qwen3-Coder |
| qwen3_code_fixC | Fix bugs in code using Qwen3-Coder |
| qwen3_code_optimizeC | Optimize code using Qwen3-Coder |
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 5 tools
Each tool has a clearly distinct purpose: explain, fix, generate, optimize, and review code. There is no overlap in functionality, and the descriptions make it easy for an agent to select the right tool for each specific task.
All tool names follow a consistent verb_noun pattern with the prefix 'qwen3_code_' followed by a specific action (explain, fix, generate, optimize, review). This predictable naming scheme enhances readability and usability.
With 5 tools, the server is well-scoped for code-related tasks. Each tool serves a distinct and essential function in the coding workflow, making the count appropriate and efficient for the domain.
The toolset covers key code operations (explain, fix, generate, optimize, review), but minor gaps exist, such as the lack of tools for code testing or refactoring. However, the core workflows are well-covered, and agents can work around these omissions.