J-Link MCP

Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.

What does this entry provide?

J-Link MCP is an MCP server entry in ChatHome Skills, sourced from Official MCP Registry and scored 73/100. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding J-Link MCP to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: Official MCP Registry
Quality: 73/100
Install method: npm
Repo: Klievan/jlink-mcp
Repo updated: Aug 28, 2026

Install command

npx -y jlink-mcp@0.6.0

Install method: npm

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Aug 28, 2026

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.

MCP manifest

{
  "_meta": {
    "io.modelcontextprotocol.registry/official": {
      "status": "active",
      "isLatest": true,
      "updatedAt": "2026-08-28T08:39:57.503509Z",
      "publishedAt": "2026-08-28T08:39:57.503509Z",
      "statusChangedAt": "2026-08-28T08:39:57.503509Z"
    }
  },
  "server": {
    "name": "io.github.Klievan/jlink-mcp",
    "title": "J-Link MCP",
    "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
    "version": "0.6.0",
    "packages": [
      {
        "version": "0.6.0",
        "transport": {
          "type": "stdio"
        },
        "identifier": "jlink-mcp",
        "registryType": "npm",
        "environmentVariables": [
          {
            "name": "JLINK_DEVICE",
            "isRequired": true,
            "description": "Target device name, exactly as J-Link spells it (e.g. nRF52840_XXAA, STM32F407VG). Use the search_devices tool to find it."
          },
          {
            "name": "JLINK_SERIAL",
            "description": "Serial number of a specific probe, when more than one is attached."
          },
          {
            "name": "SVD_PATH",
            "description": "CMSIS-SVD file for the target. Without it, peripheral reads are undecoded hex."
          },
          {
            "name": "JLINK_RTT_ADDR",
            "description": "Address of the firmware's _SEGGER_RTT symbol. Lets RTT survive a reset or flash."
          }
        ]
      }
    ],
    "repository": {
      "url": "https://github.com/Klievan/jlink-mcp",
      "source": "github"
    },
    "websiteUrl": "https://github.com/Klievan/jlink-mcp",
    "description": "Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB."
  }
}

Report an issue with this listing