This repository was archived by the owner on Sep 23, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 23, 2026. It is now read-only.
现在只有全局的mcp、subagents配置，我需要项目级别的配置 || Now there is only global mcp and subagents configuration, I need project-level configuration #1365
Description
What feature would you like to see?
在项目目录启动kimi之后能够读取项目目录的配置文件连接mcp。同样在vscode插件里启动的时候也需要能够读取项目级别的配置
Additional information
现在我只在官网找到了一个cli的启动参数--mcp-config-file，我难道要在每次启动的时候都手动添加这个参数吗？应该有一个默认读取的位置啊，只有需要额外添加的时候我再来使用这个启动参数
What feature would you like to see?
After starting kimi in the project directory, you can read the configuration file of the project directory and connect to mcp. It is also necessary to be able to read the project-level configuration when starting the vscode plug-in.
Additional information
Now I only found a cli startup parameter --mcp-config-file on the official website. Do I have to add this parameter manually every time I start it? There should be a default reading location. I will use this startup parameter only when additional additions are needed
Reacted by aiziyuer, Lraty, Macyou and Alexandr Anisimov
Reacted by Lraty
Activity
[-]现在只有全局的mcp、subagents配置，我需要项目级别的配置[/-][+]现在只有全局的mcp、subagents配置，我需要项目级别的配置 || Now there is only global mcp and subagents configuration, I need project-level configuration[/+]he-yufeng commentedon Mar 21, 2026
This would be really useful — having to pass
--mcp-config-fileevery time is tedious. Claude Code already does this with.claude/settings.local.json, and Cursor has.cursor/mcp.json.A natural convention for kimi-cli could be
.kimi/mcp.json(or.kimi/config.json) in the project root, auto-loaded at startup with the global config as fallback.Would the team be open to a PR for this? Happy to keep it minimal — just add a project-level config path lookup in the startup flow, no breaking changes to the existing
--mcp-config-fileflag.