Each MCP server you configure is started as a subprocess and its tools are merged into seek's tool set alongside built-in tools.

每个 MCP server 启动为子进程，其工具与 seek 内置工具合并。

Config File

配置文件

~/.seek/mcp.json — compatible with Claude Code and Cursor format, so you can reuse an existing mcp.json unchanged.

~/.seek/mcp.json，与 Claude Code 和 Cursor 格式兼容。

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"],
      "env": { "MY_VAR": "value" }
    }
  }
}

• command — the executable to launch
• 启动的可执行文件
• args — command-line arguments (optional)
• 命令行参数（可选）
• env — extra environment variables (optional)
• 额外的环境变量（可选）

Name Collision Rules

名称冲突

• MCP tool name = built-in tool name → built-in wins. Conflicting MCP tools are skipped with a warning on stderr.
• MCP 工具名与内置工具同名时，内置优先。冲突的 MCP 工具被跳过并输出警告。
• Two MCP servers export same tool name → the one loaded last wins (server order follows key order in mcp.json).
• 两个 MCP server 导出同名工具时，后加载的胜出。

Discovery

发现

MCP tools are merged at startup and listed alongside built-in tools when the agent decides which to call. Unlike built-in tools, MCP tools have no system-prompt-level guidance — the agent discovers them by name + description alone. Give your MCP server tools descriptive names and descriptions.

MCP 工具在启动时合并，但无系统提示层面的引导——agent 仅通过名称和描述发现它们。请给你的 MCP server 工具起描述性的名称和说明。

Design: PRD feature-mcp-client.md

设计文档：PRD feature-mcp-client.md