Trae

1. Use cases

Use OpenViking to:

• Remember technology stack preferences across sessions, including language versions, frameworks, package managers, and build systems

• Preserve coding style preferences, such as naming conventions, comment style, whether to write unit tests, and TDD/BDD habits

• Remember common project context, such as monorepo structure, build commands, deployment workflows, and environment differences

• Store historical decisions and troubleshooting notes, such as why option X was avoided or what issue happened last time with option Y

• Persist long-term personal goals, OKRs, and roadmap context so the agent can align with them while planning work

2. Trae Integration Steps for OpenViking

Trae is an AI IDE from ByteDance that natively supports loading external tools and context services through MCP. Follow the steps below in Trae.

Step 1: Open Trae settings

In the Trae main window, click Settings (gear icon) in the upper-right corner to open the settings panel.

Step 2: Open the MCP configuration page

In the left menu, select MCP to open the MCP Servers management page.

Step 3: Add an MCP Server

Click the + Add button on the right, then choose Manual configuration from the dropdown menu.

Step 4: Paste the JSON configuration

Paste the following JSON into the configuration dialog:

{
  "mcpServers": {
    "ov-mcp-server": {
      "url": "https://api.vikingdb.cn-beijing.volces.com/openviking/mcp",
      "headers": {
        "Authorization": "Bearer ZGVmYXV********YzdlZjhiMg"
      }
    }
  }
}

Step 5: Confirm and enable

Click Confirm. Trae automatically establishes the MCP connection and loads the tool list. When the connection succeeds, ov-mcp-server appears in the configured MCP Servers list. After setup, you can see that ov-mcp-server is loaded and enabled on the MCP management page, with the switch on the right shown in green.

Step 6: Check MCP connectivity

After connecting, it is recommended to run two simple queries in Trae to verify that MCP is working correctly:

1. ov ls - List the OpenViking root directory contents to confirm the connection is available and the directory structure is returned correctly:

ov ls

2. ov health - Call the health tool to confirm the OpenViking server status and current user identity:

ov health

Acceptance criteria: ov ls returns directories such as agent / resources / session / user; ov health returns service initialized and the current username, which means the integration succeeded.

3. Configuration fields

4. FAQ