Skip to content

TRAE

TRAE can launch Ark automatically after its MCP connection is configured. Tell your setup agent whether you use IDE or Work, International or CN, and a local or cloud execution environment.

  1. In a coding session with terminal and file access, use the guided setup request and name your TRAE edition as the target.
  2. Let the agent prepare Ark and resolve the configuration paths. Enter keys in the private editor, not in chat.
  3. If user-level registration requires the MCP settings UI, paste the agent-prepared non-secret entry there and enable ark-seed.

For local setup, select local runtime. A cloud runtime cannot use your computer’s paths or credential file. Do not transfer keys to a cloud host without a separate, deliberate setup decision.

Manual configuration, scope and runtime options
  • User/global default: use the selected edition’s MCP settings UI. In IDE, look for Settings > MCP > Add > Manual configuration. In Work, look for Settings > MCP > Create > Manual configuration. Confirm the selected scope in the actual UI.
  • Project: the repository’s IDE template uses <project>/.trae/mcp.json with project-level MCP enabled in settings. Verify support in your edition. Do not claim global setup by writing a project file.
  • Execution host: select local runtime for this guide. Work editions may offer local/cloud selection. Cloud requires a checkout, uv, and private credentials accessible on that cloud host; local paths will not work. Do not transfer credentials to another host without explicit approval.

Do not guess a global ~/.trae/mcp.json path from the existence of that directory. If the edition only offers a UI for user-level setup, use the UI.

Complete the shared prerequisites. Paste this JSON into the supported manual configuration UI, or merge the entry into the supported project file. Replace each placeholder with an absolute path on the selected server host:

{
"mcpServers": {
"ark-seed": {
"command": "/absolute/path/to/uv",
"args": [
"--directory",
"/absolute/path/to/ark-mcp",
"run",
"--locked",
"--no-sync",
"python",
"-m",
"ark_mcp"
],
"env": {
"ARK_MCP_ENV_FILE": "/absolute/path/to/private/ark-mcp/.env",
"MCP_TRANSPORT": "stdio",
"MCP_AUTH_MODE": "local"
}
}
}
}

The env contains no key values. The Ark checkout does not need to be the project being edited; do not substitute ${workspaceFolder} for its path unless that folder actually contains the prepared server checkout. Preserve existing servers and any same-name entry at a different scope.

Choose a tool-enabled chat mode and run the discovery-only check. A pending UI step is not a completed installation. Once your tools appear, try Your First Tool Call. Finish active jobs before reloading the connection.

See Integrations, Codex for an embedded Codex agent, Getting Started, Tools, and Configuration.

The IDE overview was consulted on 2026-11-10. The Work page could not be retrieved during this documentation pass; Work UI/runtime instructions follow the repository’s setup references and must be checked in the app.