Schema | McuBuddy

McuBuddy

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCUBUDDY_TOOL_PROFILE`	No	Tool profile to use. Set to 'full' to expose the complete expert catalog from earlier alpha releases.	core

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.

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`	{}

Functions exposed to the LLM to take actions

Name	Description
get_runtime_configD	–
inspect_project_memoryC	Read target-project memory or prepare a read-only onboarding proposal.
write_project_memoryC	Write canonical memory inside a confirmed target project.
match_chip_nameB	Resolve a chip alias to a backend-specific target name.
get_target_infoC	Return alias-match and device-patch info for a target on a given backend.
list_tool_safetyC	List safety levels for public McuBuddy tools.
list_validation_recordsB	List machine-readable real-hardware validation records.
pack_diagnoseB	Find and checksum-verify the managed CMSIS-Pack for a target.
configure_probeB	Set probe connection parameters. Run list_connected_probes first to find unique_id.
configure_elfB	Set the ELF/AXF file path for symbol resolution.
doctorB	Run a read-only environment, dependency, probe, target, and config preflight.
first_contactC	Run the safest first board contact flow and suggest next debug tools.
list_connected_probesA	List all probes currently connected to this machine. Start here if unsure what probe to use.
probe_connectD	–
read_stopped_contextD	–
elf_loadD	–
disconnect_allD	–
finish_debug_sessionB	Stop registered actuators, reset and run the target, then disconnect.
svd_loadA	Load a CMSIS-SVD file to enable peripheral register interpretation. SVD files define the register map of a chip. You can find SVD files in your chip vendor's SDK, or at https://github.com/posborne/cmsis-svd-data Example: svd_load('/path/to/STM32L496.svd')

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cunjun/McuBuddy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server