mcp-bitbake
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_recipe_filesA | Search recursively for .bb/.bbappend files matching a filename query under root_path. |
| scan_layer_recipe_filesB | List all .bb/.bbappend files under a Yocto layer path. |
| parse_recipe_fileA | Parse a single .bb or .bbappend file and return all raw variable assignments. Never evaluates variables. |
| get_recipe_var_rawB | Get all raw assignments for a specific variable in a .bb or .bbappend file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.