Trae

Add Runstack MCP in Trae IDE (ByteDance) — MCP Marketplace or .trae/mcp.json with Streamable HTTP or stdio.

Source: https://runstack.engineer/docs/mcp-trae

trae

Trae (ByteDance) is an AI-native IDE (v1.3.0+) with MCP + .rules support. Connect Trae's agent to Runstack's MCP tools at https://app.runstack.engineer/mcp (Streamable HTTP, Authorization: Bearer rnsk_…). Get a key at API Keys.

Add via Marketplace (UI)

Trae → Settings → MCP (or MCP Marketplace).
Click Add Server → choose Remote (HTTP) or Local (stdio).
Fill:

Name: runstack
Transport: Streamable HTTP (fallback SSE auto) — or Stdio for local
URL: https://app.runstack.engineer/mcp
Headers: {"Authorization": "Bearer rnsk_YOUR_API_KEY"}
For stdio: Command: npx, Args: ["-y", "@rnsk/mcp"], Env: {"RUNSTACK_API_KEY": "rnsk_YOUR_API_KEY"}

Save → agent picks up tools without restart.

trae-agent also supports mcp_servers in its Python config (legacy JSON) — IDE JSON below is preferred for Runstack.

Config files

Trae reads MCP servers from JSON similar to Cursor (global vs project):

Scope	File
Global	`~/.trae/mcp.json` (or `~/.cursor/mcp.json` compatibility shim)
Workspace	`.trae/mcp.json` at project root (or `.cursor/mcp.json` / `.trae/mcp_servers.json` legacy)

Workspace wins over global. Both use mcpServers top-level key. Trae supports three transports: stdio, sse, streamableHttp.

Manual JSON

Remote (Streamable HTTP) — recommended

{
  "mcpServers": {
    "runstack": {
      "type": "streamableHttp",
      "url": "https://app.runstack.engineer/mcp",
      "headers": {
        "Authorization": "Bearer rnsk_YOUR_API_KEY"
      }
    }
  }
}

If type is not respected, omit it and keep url+headers (Trae auto-tries Streamable HTTP then SSE). sse is legacy; prefer streamableHttp.

Local (stdio) — via `@rnsk/mcp`

{
  "mcpServers": {
    "runstack": {
      "command": "npx",
      "args": ["-y", "@rnsk/mcp"],
      "env": {
        "RUNSTACK_API_KEY": "rnsk_YOUR_API_KEY"
      }
    }
  }
}

Windows UI uses cmd /c npx -y …; macOS/Linux uses npx directly.

Verify

In Trae chat: “Use Runstack to search for Linear issue tools”. Confirm search_tools, check_authentication, initiate_connection, execute_tool are listed under MCP tools. OAuth for Gmail/GitHub routes through Runstack via initiate_connection when check_authentication reports token_missing.

Troubleshooting

No tools: Restart Trae agent after saving JSON; confirm trusted folder.
Auth 401: Verify Authorization header spelling and rnsk_… value.
Marketplace vs JSON conflict: Prefer one source; disable duplicate server in other scope.