Skip to main content
Glama
isakruas

ikmcp

by isakruas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ikmcp

No user-submitted related servers found.

    Related Servers

    • Chiplab

      veecle
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for simulating firmware on virtual microcontroller instances, allowing AI agents to upload, run, and read UART output from supported boards such as STM32 and Nordic.
      16
      MIT

    • firmforge

      NotchStone
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for firmware verification in MCU development, exposing a five-stage pipeline (Detect, Review, Build, Flash, Verify) as tools for AI agents to compile, flash, and verify firmware on Arduino boards.
      1
      MIT

    • stm32cubemx-mcp

      Wafleem
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables AI agents to inspect, plan, validate, and apply STM32CubeMX .ioc configuration changes, and generate STM32CubeIDE projects, ensuring safe and testable embedded-system workflows.
      9
      MIT

    • mcp-stm32cubeide-server

      Helistana
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI coding agents drive the full STM32 development loop—code generation, build, flash, debug, serial monitoring, and fault diagnosis—end to end via CubeIDE, CubeMX, CubeProgrammer, OpenOCD, and GDB.
      MIT

    • McuBuddy

      cunjun
      A
      license
      C
      quality
      A
      maintenance
      MCP server for AI-assisted MCU and embedded firmware debugging. It connects to real hardware via debug probes, inspects CPU/memory/peripherals, manages Keil builds, and provides structured evidence for fault diagnosis.
      19
      6
      MIT
    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

    B3.4/5.0

    Scored across 30 tools

    Disambiguation4/5

    Tools are grouped into distinct domains (language, stdlib, compiler/simulator, IDE tests/devices) and each has a clearly scoped purpose. A few near-neighbors like ik_compile/ik_check and the three *reference tools require attention to descriptions, but the boundaries are sufficiently explained.

    Naming Consistency3/5

    Names consistently use snake_case with ik_/ide_ prefixes, which helps group them. However, they mix noun-style (ik_reference, ide_test_api) with verb-style (ik_compile, ide_run_tests), and ik_project_analyze has an awkward noun-verb order.

    Tool Count2/5

    At 30 tools, the surface is larger than the 16-25 heavy range and contains many documentation endpoints that could potentially be consolidated. The broad IDE+compiler scope justifies some size, but the count still feels excessive for a single server.

    Completeness4/5

    The toolset covers the full language workflow: docs, grammar, stdlib, compile/check/simulate, project analysis, IDE test running, and device authoring. Minor gaps like project scaffolding or a version query are workable since templates and status tools exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources