Qwen Coding Engine

Created By
neco0013 months ago
Stop letting AI hallucinations eat your hours. With this engine, your work flows smoothly while a full SRE squad of models codes and debugs on your behalf. Are you building complex applications, only to find that AI hallucinations are eating your entire afternoon? You know the loop: You ask Claude or Cursor to fix a bug. It gives you a snippet. It breaks something else. You paste the error back. It forgets the original architecture and responds with "// ... rest of your code here". What started as a 5-minute feature turns into a 3-hour circular debugging nightmare. If this engine actually works, you are saved. The Qwen Engineering Engine (powered by the Lachman Protocol) completely stops the "two steps forward, one step back" dance. Instead of relying on a single, forgetful LLM to do everything, this MCP Server deploys a dedicated, specialized squad of Qwen models to your local codebase: - Zero Placeholders: The dedicated qwen_coder tool writes 100% complete, production-grade files. No lazy snipping. - Deep Debugging: Instead of pasting logs to Claude, the qwen_audit tool unleashes QwQ (Qwen's reasoning model) to act as your Senior Auditor. It reads the files, finds the memory leak, and tells you exactly what failed. - Architectural Immunity: Before writing code, the qwen_architect drafts a JSON roadmap and self-verifies it against your stack. If it's a bad idea, it rejects it *before* breaking your app. Why Qwen? Because running an entire squad of GPT-4o or Claude 3.5 Opus models to constantly rewrite files would cost you $50 a day. By routing this heavy lifting through Alibaba's DashScope API (Qwen 3.5 Plus & Qwen 2.5 Coder 32B), the cost is literal fractions of a cent. Let your main assistant (Claude/Antigravity/Cursor) be the Commander. Let the Qwen Engine do the heavy lifting in the trenches. Stop chatting. Start shipping.
Overview

Qwen Engineering Engine (The Lachman Protocol)

Are you building complex applications, only to find that AI hallucinations are eating your entire afternoon?

You know the loop: You ask Claude or Cursor to fix a bug. It gives you a snippet. It breaks something else. You paste the error back. It forgets the original architecture and responds with "// ... rest of your code here". What started as a 5-minute feature turns into a 3-hour circular debugging nightmare.

If this engine actually works, you are saved.

The Qwen Engineering Engine (powered by the Lachman Protocol) completely stops the "two steps forward, one step back" dance. Instead of relying on a single, forgetful LLM to do everything, this MCP Server deploys a dedicated, specialized squad of Qwen models to your local codebase:

  • Zero Placeholders: The dedicated qwen_code tool writes 100% complete, production-grade files. No lazy snipping.
  • Deep Debugging: Instead of pasting logs to Claude, the qwen_audit tool unleashes QwQ (Qwen's reasoning model) to act as your Senior Auditor. It reads the files, finds the memory leak, and tells you exactly what failed.
  • Architectural Immunity: Before writing code, the 'qwen_architect' drafts a JSON roadmap and self-verifies it against your stack. If it's a bad idea, it rejects it before breaking your app.

Why Qwen?

Because running an entire squad of GPT-4o or Claude 3.5 Opus models to constantly rewrite files would cost you $50 a day. By routing this heavy lifting through Alibaba's DashScope API (Qwen 3.5 Plus & Qwen 2.5 Coder 32B), the cost is literal fractions of a cent.

Let your main assistant (Claude/Antigravity/Cursor) be the Commander. Let the Qwen Engine do the heavy lifting in the trenches.

Stop chatting. Start shipping.

Server Config

{
  "mcpServers": {
    "qwen-coding": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\path\\to\\qwen-coding-engine",
        "run",
        "qwen-coding-engine"
      ],
      "env": {
        "DASHSCOPE_API_KEY": "your_api_key_here",
        "LP_MAX_RETRIES": "3"
      }
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
neco001
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago