Skip to main content
Glama
JannLeo

telinksdk-builder-mcp

by JannLeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to telinksdk-builder-mcp

No user-submitted related servers found.

    Related Servers

    • dbgprobe-mcp-server

      es617
      A
      license
      A
      quality
      C
      maintenance
      Stateful MCP server for driving debug probes (J-Link) to flash, debug, and inspect embedded targets. Enables AI agents to perform flash, memory, breakpoint, and ELF/SVD-aware operations conversationally.
      41
      10
      MIT

    • Firmware MCP Server

      Alooswr
      A
      license
      Not graded
      quality
      D
      maintenance
      A local stdio MCP server for embedded firmware automation that exposes tools to build, flash, reset devices, and capture serial logs through a device configuration file.
      1
      MIT

    • esp-mcp

      horw
      F
      license
      Not graded
      quality
      F
      maintenance
      An MCP server for managing ESP-IDF workflows, enabling LLMs to build, flash, and test firmware for ESP32 and related microcontrollers. It provides tools for project creation, target configuration, and serial port management to simplify embedded development.
      157
      -

    • stm32c0-mcp

      praderppp
      F
      license
      A
      quality
      C
      maintenance
      MCP server for scaffolding, building, and flashing bare-metal STM32C011 firmware using the STM32CubeCLT toolchain. Exposes tools for project scaffold, build, flash, and probe listing.
      4
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools follow a consistent <resource>_<action> pattern (e.g., build_info, flash_run, serial_list). The naming is predictable and clear.

    Tool Count5/5

    With 8 tools covering build configuration, execution, flashing, and serial verification, the count is well-scoped for an embedded firmware development workflow.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources