TRAECNclaw MCP

Operate TraeCN through TRAECNclaw's focused stdio MCP tools. Use when an MCP-capable agent must send or stop work, choose a workspace/model/mode/conversation, inspect or change Trae settings through its UI, manage conversations, or resolve an exceptional question or unsafe approval. Queueing, waiting, recovery, notifications, safe approvals, and keep/revert gates are gateway-managed.

Compose focused tools around user intent. Do not call preflight, wait, poll, event acknowledgement, recovery, cleanup, proof, process, or generic command operations from the agent loop; the gateway owns those mechanics.

Setup

1. Run npm run doctor in the repository.
2. Configure the client from assets/mcp-client-config.json, replacing SKILL_DIR with this folder's absolute path. Use assets/mcp-client-config.direct.json when directly referencing the repository server.
3. Start the gateway with npm run start:gateway, then reconnect the MCP client.
4. Use mock mode only for development; never cite mock output as live TraeCN evidence.

Choose only necessary context

• Call traecn_open_workspace only when the requested folder is not already open.
• Call traecn_list_models when the available choices matter; then call traecn_select_model once.
• Call traecn_select_mode only when the task requires a different Solo/IDE mode.
• Call traecn_list_conversations to read the current mode and stable conversation IDs.
• Use traecn_create_conversation, traecn_select_conversation, or traecn_delete_conversation for exactly one conversation operation.

These tools change TraeCN context. Never repeat workspace paths in the model message.

Send and track work

Call traecn_send_message with the exact message and, when concurrency makes the target ambiguous, an explicit conversationId. It returns only the accepted taskId and status.

Do not wait or poll after sending. The stdio server delivers compact task notifications and acknowledges them internally. Call traecn_get_task only for an intentional status/result read. Use traecn_cancel_task for one known gateway task. Use traecn_stop_generation only when the user wants the generation currently visible in TraeCN stopped. First list conversations and pass the active conversationId; the gateway rejects a stale or different conversation. Because visible work may belong to the user or another agent, set acknowledgeUntrackedWork:true and include a short audit reason. Use traecn_cancel_task instead when the work has a gateway task ID.

Inspect or change Trae settings

Treat settings as a second-level capability. Call traecn_list_setting_sections, then traecn_list_settings for only the needed section. For dropdowns, call traecn_list_setting_options instead of guessing. Use exactly one matching mutation tool:

• traecn_set_setting_toggle for a boolean switch.
• traecn_select_setting_option for a dropdown choice.
• traecn_set_setting_text for a text or numeric input.

These commands make the change through Trae's visible settings UI. The gateway serializes UI access and returns to chat automatically; do not navigate back manually or repeat reads after a successful write.

Resolve exceptional interactions

The gateway automatically approves only strict read-only shell chains. The allowlist covers directory changes, basic file inspection, and Git reads; it rejects redirection, substitution, network/process/package commands, project scripts, mutating find/sed, and external rg/Git hooks. Every automatic command approval is recorded in the local append-only audit log. Unknown or mutating commands are returned to the Agent instead.

If a task reports an unresolved interaction:

• Use traecn_answer_question for a returned question and one of its offered answers.
• Use traecn_decide_approval only after checking the returned command and risk. Approval requires the exact expectedCommand, acknowledgeRisk:true, and a short audit reason; the gateway re-reads the visible card and rejects stale or changed commands. Denial needs no risk acknowledgement.

Conversation deletion is permanent. Delete only an inactive conversation and only when the current user request explicitly names or unambiguously identifies it for deletion. Re-read its listed ID and exact title, then pass the title with acknowledgePermanentDeletion:true; the gateway rejects title mismatches and the active conversation, records the attempt, and cannot restore a successful deletion. This uses the user's existing instruction and does not add a separate confirmation round trip.

Safety

• Keep the gateway on 127.0.0.1 unless remote access is secured.
• Never expose .env, tokens, authorization headers, or TraeCN profile data.
• Keep the default security audit log enabled; high-impact approvals, stops, and deletions are written to date-based JSONL files with sensitive fields redacted and a default 30-day retention.
• Treat mock results and non-terminal task states as incomplete.
• Do not recreate removed low-level tools through shell, generic commands, or GUI control.

Read references/mcp-surface.md only for exact schemas, notification behavior, and gateway ownership boundaries.