mcp-bitbake
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-bitbake What are the raw SRC_URI assignments for the busybox recipe?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-bitbake
A deterministic MCP (Model Context Protocol) server for BitBake/Yocto. Inspects recipe metadata without evaluating variables — returns only raw assignments as found in files.
Design rules:
Never evaluates variables — only returns raw assignments
Only supports
.bband.bbappendfilesSupported operators:
=,:=,?=,+=,.=Returns structured JSON for all responses
Fails closed on unsupported syntax (override syntax warned, not parsed)
Install
From GitHub (no npm publish needed):
npm install github:pkt-lab/mcp-bitbakeOr clone and build manually:
git clone https://github.com/pkt-lab/mcp-bitbake
cd mcp-bitbake
npm install && npm run buildRelated MCP server: Repo Docs MCP
Claude Desktop configuration
If installed via npm (GitHub):
{
"mcpServers": {
"mcp-bitbake": {
"command": "node",
"args": ["./node_modules/mcp-bitbake/dist/index.js"]
}
}
}If cloned locally:
{
"mcpServers": {
"mcp-bitbake": {
"command": "node",
"args": ["/absolute/path/to/mcp-bitbake/dist/index.js"]
}
}
}Config file location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Restart Claude Desktop after editing.
MCP tools
find_recipe_files
Search recursively for .bb/.bbappend files matching a filename pattern:
{ "root_path": "/path/to/poky", "query": "busybox" }Returns: { ok: true, matches: [{ path, file_type, filename }] }
scan_layer_recipe_files
List all .bb/.bbappend files under a layer path:
{ "layer_path": "/path/to/meta-mylayer" }Returns: { ok: true, files: [{ path, file_type }] }
parse_recipe_file
Parse a single .bb or .bbappend file and return all raw variable assignments:
{ "file_path": "/path/to/meta-layer/recipes-core/myapp/myapp_1.0.bb" }Returns: { ok: true, variables: [{ name, operator, raw_value, line }], warnings?: [...] }
Comments and python/shell function blocks are skipped
Override syntax (
VAR:append,VAR:${PN}, etc.) is warned but not parsedMulti-line values (lines ending with
\) are concatenated intoraw_value
get_recipe_var_raw
Get all assignments for a specific variable in a file:
{ "file_path": "/path/to/recipe.bb", "variable": "SRC_URI" }Returns: { ok: true, assignments: [{ operator, raw_value, line }] }
Error format
All errors return:
{ "ok": false, "error_code": "...", "message": "..." }Error codes: FILE_NOT_FOUND, INVALID_PATH, UNSUPPORTED_SYNTAX, INVALID_ARGUMENT
License
MIT
Available Tools
4 toolsfind_recipe_filesA
Search recursively for .bb/.bbappend files matching a filename query under root_path.
Inputs: root_path (required), query (required).
get_recipe_var_rawB
Get all raw assignments for a specific variable in a .bb or .bbappend file.
Inputs: file_path (required), variable (required).
parse_recipe_fileA
Parse a single .bb or .bbappend file and return all raw variable assignments. Never evaluates variables.
Inputs: file_path (required).
scan_layer_recipe_filesB
List all .bb/.bbappend files under a Yocto layer path.
Inputs: layer_path (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
The tools have mostly distinct purposes: find_recipe_files searches by filename, get_recipe_var_raw extracts a specific variable, parse_recipe_file parses all variables in a file, and scan_layer_recipe_files lists files in a layer. However, find_recipe_files and scan_layer_recipe_files both involve listing recipe files, which could cause some confusion about when to use each.
All tool names follow a consistent verb_noun pattern with snake_case, such as find_recipe_files, get_recipe_var_raw, parse_recipe_file, and scan_layer_recipe_files. This uniformity makes the set predictable and easy to understand.
With 4 tools, the count is reasonable for a BitBake/Yocto-focused server, allowing for basic operations like searching, parsing, and listing. It might be slightly thin for advanced workflows, but it covers core needs without being overwhelming.
The tools provide good coverage for reading and parsing recipe files, but there are notable gaps for actions like evaluating variables, modifying recipes, or handling dependencies. This limits the server to inspection tasks, missing key operations for a full BitBake toolset.
Maintenance
Related MCP Connectors
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
An MCP server that provides tools to discover and retrieve podcast episodes transcripts.
Public MCP server for discovering open jobs. Search, filter, and get application links.
MCP registry & directory: search, find & install 31k+ MCP servers & tools. Catalog and marketplace.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that scans codebases to extract structural information (classes, functions, etc.) with flexible filtering options and outputs in LLM-friendly formats.12GPL 3.0
- AlicenseNot gradedqualityDmaintenanceA generic MCP server that exposes local repository checkouts, allowing users to search and read code and documentation through natural language. It supports multiple instances, enabling seamless interaction with various codebases via configurable tool prefixes and URI schemes.2,128 npmMIT
- AlicenseAqualityDmaintenanceA local-first MCP server that enables AI tools to safely inspect and search code repositories, providing indexing, deterministic BM25 search, code outlining, and context bundles without code modification.91MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for local-first lexical code search, providing tools for searching code, finding symbols, and reading chunks from indexed repositories.MIT