Kconfig Mcp

io.github.0xmortuexPublished by GitHub account 0xmortuexv0.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Explains why a Kconfig symbol (e.g. CONFIG_X) can't be enabled, with file:line dependency chains and a verified minimal fix.

What you can do
  • Load and manage Kconfig source trees, optionally with an existing .config, into named sessions
  • Explain why a bool or tristate symbol is not y/m/n, recursively with file:line, plus a verified minimal fix and its side effects
  • Inspect a symbol's type, prompt, value, assignable values, dependencies, defaults, select/imply links and help text
  • Find every symbol that selects or implies a given one, and regex-search names, prompts and help
  • Assign values as menuconfig would, reporting every other symbol that changed, and diff against another config, defconfig or fragment
  • Write a .config or a minimal defconfig
When to use it
Useful when configuring the Linux kernel, Zephyr, U-Boot or Buildroot and an option is missing or greyed out in menuconfig, or when you need to know what a change will switch on or off before editing a config.
Requirements
Local Python 3.10+ process installed from PyPI (kconfig-mcp). A source tree containing the Kconfig files is needed, even a sparse checkout; no kernel build environment is required. For Linux, pass arch variables such as SRCARCH and ARCH when loading, and optionally shell="dry" when no compiler is available.
Before you install
kconfig_set and kconfig_save change configuration state: assignments can silently flip other symbols through select, imply or defaults, and saving writes a .config or defconfig file. With the default shell="run" mode the tree's shell calls are executed with a POSIX sh, as make menuconfig would; use shell="dry" to run nothing. Dry mode makes compiler-probe symbols read as absent.

Installation

In SourceWeft

  1. Open Kconfig Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 6a23bfb

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 11, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts