Traecnclaw MCP server
io.github.Luckycat133/traecnclaw·v0.6.0Local persistent TraeCN coding-task gateway with a focused MCP Agent surface.
0 stars38 downloads/wk
Reviews
Write oneNobody has reviewed Traecnclaw yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Traecnclaw tools (20, 4 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
traecn_answer_questionResolve an exceptional question from TraeCN that the gateway could not handle mechanically by supplying the user's decision. The gateway routes the answer to the pending visible prompt and reports the outcome. Only call when a pending interaction exists.
traecn_cancel_taskwrite actionCancel one gateway-tracked task by ID. The gateway stops shepherding the work at its next control point and records the cancellation; results already produced remain in task history. Returns the task identity and post-cancellation status.
traecn_create_conversationwrite actionCreate a new TraeCN conversation and make it the active target. Every call creates an additional conversation, so call at most once per genuinely new context. Returns the created conversation identity.
traecn_decide_approvalApprove or deny the unsafe or ambiguous command card currently visible in TraeCN. Approval revalidates the exact expectedCommand against the card and requires acknowledgeRisk plus an audit reason recorded locally; denial needs only the decision. Never approve beyond the scope the user authorized.
traecn_delete_conversationwrite actionPermanently delete one inactive TraeCN conversation by stable identifier. Requires the exact expectedTitle returned by traecn_list_conversations plus an explicit irreversible-deletion acknowledgement; there is no gateway recovery path.
traecn_get_taskRead one known gateway task by ID: status plus final result, or the full execution trace with detailLevel 'trace' for diagnosis. Call once when notified of completion or once later when resuming after a disconnect. Not a progress primitive — do not poll in a tight loop.
traecn_list_conversationsList the conversations available in the current TraeCN mode with stable identifiers accepted by conversation-scoped tools. Read-only; call when choosing or verifying conversation context.
traecn_list_modelsList the model names currently offered in the TraeCN UI together with the currently selected model. Read-only discovery; call before select_model whenever the model choice matters.
traecn_list_setting_optionsList the visible choices of one dropdown-style setting identified by section and label. Required before select_setting_option; never invent an option value.
traecn_list_setting_sectionsList the settings sections currently visible in TraeCN's settings UI. Required first step for any settings operation; never guess a section name.
traecn_list_settingsList the individual settings and their control types within one section returned by traecn_list_setting_sections. Read-only discovery preceding any setting mutation; never guess a label.
traecn_open_workspaceOpen one absolute local folder path as the active TraeCN workspace and verify it became active before returning. Call before submitting work that depends on a specific project; afterwards do not repeat the path inside the task message.
traecn_select_conversationMake one existing conversation the active target for subsequent visible interaction. Returns the confirmed active conversation identity.
traecn_select_modeSwitch TraeCN between Solo and IDE mode and confirm the resulting active mode. Switching to the current mode succeeds as a no-op. Call only when the requested mode differs.
traecn_select_modelSelect one model by exact name from traecn_list_models and confirm the picker state before returning. Selecting the already-active model succeeds as a no-op. Does not wait for model availability or capacity.
traecn_select_setting_optionSelect one previously listed option for a dropdown setting identified by section and label, and confirm the applied selection. Only values returned by traecn_list_setting_options are valid.
traecn_send_messagewrite actionSubmit one user instruction to TraeCN as durable background work and return its stable taskId immediately; the gateway owns queueing, retries, recovery, and result persistence. Use this for every delegated coding request, optionally targeting an existing conversation via conversationId. Do not send follow-up messages to probe progress — track the returned task instead.
traecn_set_setting_textEnter one text value into the setting field identified by section and label, and confirm what the field contains afterwards.
traecn_set_setting_toggleEnable or disable one toggle setting identified by section and label, then read back the applied state. Applying the already-current state succeeds as a no-op.
traecn_stop_generationStop only the generation currently visible in the named active TraeCN conversation. Visible output may belong to the user or another agent, so this requires acknowledgeUntrackedWork=true plus an audit reason. Prefer cancel_task whenever a gateway task ID exists.
Public scan report
scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it
- Code scan120 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Traecnclaw compares
Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 83/100
- higher than 60% of 1,299 Productivity servers
- Tools
- 20
- the typical Productivity server has 7
- Tools that change things
- 20%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 38
- more than 26% of 427 Productivity servers with a package
What its tools let an agent do: 16 read · 4 change
Install Traecnclaw in Claude Code, Cursor or VS Code
Runs npx -y @luckycat133/traecnclaw on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add traecnclaw -- npx -y @luckycat133/traecnclaw
What the publisher says
From the Traecnclaw repository's README, as published. We do not edit it. Read it on GitHub
TRAECNclaw MCP Skill
Generated from canonical TRAECNclaw 0.6.0 at commit 40bcf7707ed9b0ff7938aea8e511d0b87d300705.
TRAECNclaw is a local-first MCP server and Agent Skill for operating the TraeCN desktop app on the user's Mac. This repository is the public distribution mirror: it carries the portable Skill, installable server archives, provenance, and marketplace metadata without publishing the private canonical history.
TRAECNclaw exposes MCP contract version 5 with exactly 20 stable, single-intent tools. The normal Agent flow is:
hosts can negotiate Tasks and subscribe to the exact returned task ID.
- Open a workspace only when needed.
- Select model or mode only when needed.
- Send one message and release the caller context.
- Legacy MCP clients receive a durable notification; modern 2026-07-28
Queueing, waiting, recovery, routine non-command questions, task ownership, and durable completion remain gateway-managed.
The local server uses newline-delimited stdio, implements MCP 2026-07-28, and remains compatible with initialization-based 2025-11-25 and 2024-11-05 clients. TRAECNclaw contract version 5 is the tool-surface version, not the MCP protocol revision. The independently negotiated, upstream-draft io.modelcontextprotocol/tasks extension does not add tools.
Install the server
Install the exact release through one verified channel:
npm install --global @luckycat133/traecnclaw@0.6.0
# or, after `brew info` reports 0.6.0
brew install Luckycat133/tap/traecnclawThe matching GitHub Release also provides the complete scoped npm tarball and deterministic MCPB bundle. The unrelated unscoped traecnclaw@0.3.1 package is historical and is not a current install path.
Install the Agent Skill
Install from the public GitHub repository with the open Skills CLI:
npx skills add https://github.com/Luckycat133/traecnclaw-mcp-skill \
--skill traecnclaw-mcp \
-gOr download the matching Skill archive from the GitHub Release. The Skill lives at .codex/skills/traecnclaw-mcp and includes assets/mcp-client-config.json, scripts/setup-mcp.js, and the server launcher. Restart the Agent host after installing or updating the Skill.
Use scripts/setup-mcp.js to validate server discovery and generate the host entry. The normal runtime is:
Agent host -> local stdio server -> gateway on the same Mac -> TraeCNThe server and gateway run on the same user-owned Mac as TraeCN. Marketplace containers may inspect the stdio schema, but a cloud container cannot transparently control the user's local TraeCN desktop.
Prepared Official Registry metadata uses the scoped package @luckycat133/traecnclaw@0.6.0 with local stdio transport. Smithery Local uses the matching verified MCPB bundle; the retired smithery.yaml format remains absent.
Configuration
The gateway defaults are TRAECNGATEWAYHOST=127.0.0.1 and TRAECNGATEWAYPORT=8788. Non-loopback binds require TRAECNGATEWAYTOKEN. There is no MCP tool-profile setting.
Discovery channels
The same public repository is the canonical source for Skill and MCP directory submissions. A directory listing is trustworthy only when its version, local stdio transport, macOS requirement, 20-tool count, and generated install command match this Release.
Selected channels include ClawHub, Glama, skills.sh, AwesomeSkills.dev, MCP.Directory, MCPB/Smithery Local, and—after a current public package exists—the Official MCP Registry and PulseMCP. Other directories should reuse the same provenance and install copy rather than maintaining forks.
Glama
glama.json and the generated root Dockerfile support directory registration, maintainer verification, security/quality scanning, and tool-schema inspection. The Dockerfile installs the current public Release and never contains a gateway token or mock bridge.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Traecnclaw: common questions
- Is Traecnclaw MCP server safe?
- Mostly: it is graded B (83/100). Read the Traecnclaw safety report
- How do I install Traecnclaw?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Traecnclaw need an API key?
- Yes. The registry entry asks for
TRAECN_GATEWAY_TOKEN. - Is Traecnclaw maintained?
- The last commit was 3 days ago (2026-11-01). The latest release is v0.6.0.
- What can I use instead of Traecnclaw?
- Servers from other publishers that do the same job: CLEO MCP Server, Argent MCP server and Joxo MCP server.
- How does Traecnclaw compare with other Productivity MCP servers?
- safety score 83/100 (higher than 60% of 1,299 Productivity servers); tools 20 (the typical Productivity server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Traecnclaw
Same job from other publishers: the closest match first, then the best rated.
- CLEO MCP ServerTask management for AI coding agents — CQRS 2-gateway pattern, 200 ops across 10 domainsnot reviewedEstablishedB
- ArgentDrive iOS Simulators, Android emulators, TVs and Electron/web apps from your coding agentnot reviewedWidely usedA
- JoxoOne shared project for a team's coding agents: decisions, a task board and handoffs.not reviewedGrowingA
GodPrompt MCP ServerGodPrompt MCP + Agent Skill for coding agents with TDD, debugging, verification, and task routing.not reviewedGrowingA- WTFMYour coding agent writes the user docs from your codebase, screenshots included.not reviewedGrowingA