telinksdk-builder-mcp
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_infoA | Show the builder config for the current project (parameters, presets, artifacts config, toolchain). No build is performed. |
| build_presetsC | List the named build presets defined in this project's builder.json. |
| build_runA | Run a build using the project's builder.json. Pass either a preset name and/or explicit parameter overrides (e.g. {"Target":"tx"}). Output artifacts are scanned afterwards. |
| build_listA | List collected build artifacts (from the directories configured in builder.json 'artifacts.scan_dirs'). |
| serial_listA | List available serial ports on this machine (cross-platform: COMx on Windows, /dev/tty* on Linux/macOS). Requires pyserial. |
| serial_captureA | Open a serial port and capture its output for a bounded duration. Useful to verify firmware behavior after flashing: read the UART log and let the agent judge if 'boot ok' / version string / expected output appears. Port/baud default to builder.json 'serial' section; auto-picks first port if none given. |
| flash_infoA | Show the 'flash' section of builder.json (default chip, bdt_path, timeout, reset_after_flash). Does not invoke bdt. |
| flash_runA | Invoke Telink bdt.exe to write/read flash/core/otp/analog or reset the chip. Reads builder.json 'flash' section for defaults (chip, bdt_path). Use wf to flash firmware (auto-picks latest .bin from build_variants if no input_file), rst -f to reset, rf to read back. Auto-resets after wf unless reset_after_flash=false. |
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 8 tools
Each tool targets a distinct action: build configuration, artifact listing, preset listing, building, flash config, flashing, serial capture, and port listing. No overlap in purpose.
All tools follow a consistent <resource>_<action> pattern (e.g., build_info, flash_run, serial_list). The naming is predictable and clear.
With 8 tools covering build configuration, execution, flashing, and serial verification, the count is well-scoped for an embedded firmware development workflow.
The surface covers the core workflow from config to flash to serial verification. A minor gap is lack of a tool to modify builder.json directly, but overrides are supported via build_run.