board-spec-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOARD_SPEC_REPO_URL | No | Remote to clone/fetch | git@github.com:roshs189/board-spec.git |
| BOARD_SPEC_CACHE_DIR | No | Local bare-ish clone location | ~/.cache/board-spec-mcp/repo |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | List all board (machine) names available as branches in the board-spec repo. |
| get_board_specA | Return the full board spec (machine_creation + partition_conf sections) for a machine. Raises if no branch named |
| get_machine_creation_fieldsB | Return only the machine_creation section of a board's spec. Use this from the qcom-yocto-new-machine skill instead of parsing a Confluence page's Board Identity / Disk Configuration sections. |
| get_partition_conf_fieldsA | Return only the partition_conf section of a board's spec. Use this from the qcom-partition-conf-new-board skill instead of parsing a Confluence page's Partition Table / contents.xml.in Metadata sections. |
| validate_board_specA | Schema-validate a board spec and run the cross-checks the skills used to do by hand against a Confluence page: delta=new partitions must have notes and must not collide with SoC-mandated names (xbl/tz/hyp/aop/...), partition_files_subdir must match partitions//, reference_board should exist, and chip IDs should not collide across boards. Returns {valid, schema_errors, warnings}. schema_errors block automation; warnings should be surfaced to a human but don't block by themselves. |
| refresh_specsA | Fetch the latest branches/commits from the board-spec remote. Call this if a spec was just pushed/updated and you need the MCP to see it without restarting the server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/roshs189/board-spec-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server