
Traecnclaw
io.github.Luckycat133Published by GitHub account Luckycat133v0.6.0Updated Oct 24, 2026
Local persistent TraeCN coding-task gateway with a focused MCP Agent surface.
Overview
A local MCP server that lets an assistant drive the TraeCN desktop coding app on the user's Mac through a local gateway.
- What you can do
- Open a TraeCN workspace when needed and select a model or mode for the session. Send a single message to TraeCN and release the caller context while the gateway handles queueing, waiting and recovery. Receive durable completion notifications, or negotiate Tasks and subscribe to the returned task ID on newer hosts. Exposes a fixed surface of 20 single-intent tools over local stdio.
- When to use it
- Use it when you want an AI assistant to hand coding tasks to the TraeCN desktop app running on the same Mac and get notified when they finish. It is not meant for cloud or container hosts that cannot reach the user's local desktop.
- Requirements
- Runs as a local process on macOS alongside the TraeCN desktop app, installed from the npm package or a Homebrew tap. A gateway runs on the same Mac; defaults are TRAECN_GATEWAY_HOST 127.0.0.1 and TRAECN_GATEWAY_PORT 8788. Non-loopback binds require TRAECN_GATEWAY_TOKEN. The agent host must be restarted after installing or updating.
Installation
In SourceWeft
- Open Traecnclaw in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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:
- 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-28hosts can negotiate Tasks and subscribe to the exact returned task ID.
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:
The matching GitHub Release
also provides the complete scoped npm tarball and deterministic MCPB bundle.
The unrelated unscoped [email protected] package is historical and is not a
current install path.
Homebrew compatibility transition
This repository also carries Formula/traecnclaw.rb, copied byte-for-byte from
the existing public 0.6.0 tap. Luckycat133/homebrew-tap remains available during
the transition. Existing installations do not change automatically. See
migration, checks and rollback before changing a tap
remote. The Skill, source revision and historical release downloads are unchanged.
Install the Agent Skill
Install from the public GitHub repository with the open Skills CLI:
Or 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:
The 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/[email protected] with local stdio transport. Smithery Local
uses the matching verified MCPB bundle; the retired smithery.yaml format
remains absent.
Configuration
The gateway defaults are TRAECN_GATEWAY_HOST=127.0.0.1 and
TRAECN_GATEWAY_PORT=8788. Non-loopback binds require
TRAECN_GATEWAY_TOKEN. 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.
TRAECNclaw should be listed as a local stdio server. Do not describe a Glama hosted container as an automatic remote connection to the user's Mac.
See SOURCE_REVISION and release-manifest.json for provenance and channel
readiness.
Source: README.md at commit 2407f57
Tools
0Version history
1- v0.6.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts