Kconfig Mcp

io.github.0xmortuex由 GitHub 帳號 0xmortuex 發布v0.1.0更新於 Oct 24, 2026

Why can't I enable CONFIG_X? Explains Kconfig dependencies and finds a verified fix.

已驗證STDIO僅桌面檔案與儲存開發者工具

概覽

AI 產生的概覽

解釋 Kconfig 選項(例如 CONFIG_X)為何無法啟用,提供含檔案與行號的相依鏈,以及經過驗證的最小修正方案。

可以做什麼
  • 將 Kconfig 原始碼樹(可附帶現有 .config)載入為具名工作階段並管理多個工作階段
  • 遞迴解釋 bool 或 tristate 選項為何不是 y/m/n,附檔案與行號,並給出經驗證的最小修正及其副作用
  • 檢視選項的型別、提示、值、可指定值、相依性、預設值、select/imply 雙向關係與說明文字
  • 列出所有 select 或 imply 該選項的符號,並以正規表示式搜尋名稱、提示與說明文字
  • 像 menuconfig 一樣指定值並回報隨之變動的其他選項,與另一份設定、defconfig 或片段比對
  • 寫出 .config 或最小 defconfig
適用情境
適合在設定 Linux 核心、Zephyr、U-Boot 或 Buildroot 時,某個選項在 menuconfig 中消失或變灰,或需要在改動設定前先了解會連帶開啟或關閉哪些選項。
執行需求
在本機執行 Python 3.10+ 程序,從 PyPI 安裝 kconfig-mcp。需要含 Kconfig 檔案的原始碼樹,稀疏檢出即可,不需核心建置環境。載入 Linux 時需傳入 SRCARCH、ARCH 等架構變數,沒有編譯器時可使用 shell="dry"。
安裝前請注意
kconfig_set 與 kconfig_save 會改動設定狀態:指定值可能透過 select、imply 或預設值悄悄改變其他選項,儲存則會寫入 .config 或 defconfig 檔案。預設 shell="run" 模式會像 make menuconfig 一樣以 POSIX sh 執行原始碼樹中的 shell 呼叫;改用 shell="dry" 則完全不執行,但編譯器探測類選項會讀為不存在。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Kconfig Mcp,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

kconfig-mcp

"Why can't I enable CONFIG_X?", answered with file:line and a fix that's been checked.

kconfig-mcp is an MCP server that lets an AI agent reason about Kconfig, the configuration system used by the Linux kernel, Zephyr, U-Boot, Buildroot and others.

Everyone who has configured a kernel has hit this: the option you want isn't in menuconfig, or it's there but greyed out, and the reason is five depends on hops away in a different directory. kconfig-mcp walks that chain for you. Then it searches for the smallest set of changes that would unlock the option, and applies them to the real tree to verify they work before it shows them to you.

What it looks like

This is real output on the current Linux tree (18,913 symbols) for x86:

> kconfig_why_not X86_X2APICX86_X2APIC = n (default), needs y - bool at arch/x86/Kconfig:463  its prompt (arch/x86/Kconfig:463) is visible only if  X86_LOCAL_APIC && X86_64 && (IRQ_REMAP || HYPERVISOR_GUEST), which is n:    needs any one of (2 options, all currently too low):      IRQ_REMAP = n (default), needs y - bool at drivers/iommu/Kconfig:201        its prompt is visible only if X86_64 && X86_IO_APIC && PCI_MSI && ACPI && IOMMU_SUPPORT:          PCI_MSI = n (default), needs y - bool at drivers/pci/Kconfig:44            its prompt is visible only if PCI, which is n:              PCI = n (default) - set PCI=y directly.      HYPERVISOR_GUEST = n (default), needs y - bool at arch/x86/Kconfig:787        its prompt is visible - set HYPERVISOR_GUEST=y directly.
Verified fix (2 change(s)): HYPERVISOR_GUEST=y, X86_X2APIC=y  HYPERVISOR_GUEST: arch/x86/Kconfig:787  X86_X2APIC: arch/x86/Kconfig:463Unverified alternatives: PCI=y, PCI_MSI=y, IRQ_REMAP=y, X86_X2APIC=y
> kconfig_set HYPERVISOR_GUEST yCONFIG_HYPERVISOR_GUEST: 'n' -> 'y'.1 other symbol(s) changed as a consequence: X86_X2APIC n->y

The same question on a 32-bit build (ARCH=i386) ends somewhere no symbol change can reach, and the tool says so instead of inventing a fix:

64BIT = n (default), needs y - bool at arch/x86/Kconfig:3  requires "i386" = "x86", which compares two constants and is always false here.  One side was probably expanded from an environment variable (like $(ARCH)) when  the tree was loaded: no symbol change can fix this - reload with a different env.No verified fix: every route ends in something no assignment can change.

Why it's built this way

  • Fixes are verified, not guessed. Kconfig is full of edge cases: tristate m needs MODULES, bools promote m to y, choices deselect their other members, select overrides depends on, and default y turns things on silently. So every candidate plan is applied to the loaded tree and checked. Only plans that really reach the goal are shown as fixes, together with their side effects (what else select/imply/defaults switch on or off).
  • It parses current Linux. It's built on Kconfiglib, which hasn't had a release since 2020 and can't parse Linux's newer modules, transitional and depends on X if Y syntax. kconfig-mcp rewrites those lines as files are read, keeping every line number exact. depends on X if Y is lowered with a line-by-line port of expr_trans_compare from scripts/kconfig/expr.c, so it behaves exactly as kconfig does, including how kconfig treats !S when S is m.
  • Environment problems are named. Linux sources arch/$(SRCARCH)/Kconfig, and an unset variable silently becomes "". kconfig-mcp tracks undefined variables and names them in the error (undefined variable(s): SRCARCH (the arch/ directory to use, ...)) instead of leaving you with arch//Kconfig not found.

Install

bash
pip install kconfig-mcpclaude mcp add kconfig -- kconfig-mcp

Python 3.10+. You don't need a kernel build environment. A source tree with its Kconfig files is enough, even a sparse checkout:

bash
git clone --depth 1 --filter=blob:none --sparse https://github.com/torvalds/linux.gitcd linux && git sparse-checkout set --no-cone '/Kconfig' '**/Kconfig*' '/arch/*/configs/*'

Loading trees

Treekconfig_load arguments
Linuxkconfig_path="linux/Kconfig", env={"SRCARCH": "x86", "ARCH": "x86"} (or arm64/arm64, riscv/riscv, ...). Add config_path=".config" for an existing config.
Linux, no compiler / Windowsthe same plus shell="dry"
Any other treethe top-level Kconfig plus whatever variables it expands. A load error names each missing one.

shell controls the tree's $(shell,...) calls, which is how Linux probes the compiler:

  • "run" (default) runs them with a POSIX sh, as make menuconfig would. Compiler-dependent symbols then reflect your real toolchain.
  • "dry" runs nothing. Linux's probe idioms get fixed answers: feature probes read as absent, and the toolchain reports as GCC 13.2. $(error-if) checks become warnings. Results then carry a note that compiler-dependent symbols such as CC_HAS_* read as absent.

Tools

ToolWhat it does
kconfig_loadParse a tree (plus optional .config) into a named session. Reports undefined variables and warnings.
kconfig_why_notThe unmet conditions behind symbol not being y/m/n, recursively with file:line, plus a verified minimal fix and its side effects.
kconfig_symbolType, prompt, value and why it has that value, assignable values, dependencies, defaults, select/imply in both directions, help text.
kconfig_what_selectsEvery symbol that selects or implies this one, with current values and which are active.
kconfig_searchRegex search over names, prompts and help, with name matches first.
kconfig_setAssign a value as menuconfig would, and report every other symbol that changed. A refused assignment says so.
kconfig_diffCompare with another .config, or with a defconfig or fragment using fragment=True.
kconfig_saveWrite .config, or a minimal defconfig with minimal=True.
kconfig_sessions / kconfig_unloadManage loaded trees.

Symbol names work with or without CONFIG_. A misspelt name gets "Did you mean: ...".

Limitations

  • transitional symbols are always n. Real kconfig reads them from an old .config to migrate a value during a rename. Kconfiglib has no equivalent.
  • The fix search is bounded. Selects and defaults are only explored when a symbol can't be reached through its own prompt, and the search has an expansion budget. If no verified fix is found, the result says whether the budget ran out or every route is genuinely blocked.
  • why_not covers bool and tristate symbols. For int/hex/string symbols, use kconfig_symbol and kconfig_set.
  • Dry mode answers compiler probes generically (see above), so trust CC_HAS_*-style symbols only with shell="run" on a real toolchain.
  • It depends on Kconfiglib 14.1.0, pinned because compat.py hooks two of its internal methods. CI parses the latest Linux tree every week, so the next new keyword shows up as a failing build rather than a silent wrong answer.

Tests

bash
pip install ".[test]" "ruff==0.16.0" "mypy==2.3.0"ruff check src tests && mypy --strict srcpytest tests                                   # unit + stdio tests, fixture treesLINUX_SRC=/path/to/linux pytest tests/test_linux_integration.py

The fixture tree in tests/fixtures/tree exercises every construct the explainer handles: depends on, select, imply, choice, visible if, menuconfig/if blocks, defaults, tristate and modules, and an arch directory chosen by $(SRCARCH). The Linux tests assert real facts, such as x2APIC's dependencies, the i386 dead end, and the x86_64 defconfig already enabling it. CI runs them against a sparse checkout of the current tree.

License

MIT. Kconfiglib is ISC-licensed.

來源:README.md,提交 6a23bfb

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.0最新Oct 11, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分