MCPNav
J

J-Link MCP

MCP server · by Klievan

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

Install

Run one of the commands below, then add the client config underneath.

npm
npx -y jlink-mcp

Client configuration

Paste into Claude Desktop, Cursor (mcp.json), VS Code or any MCP client, then restart the client.

mcpServers
{
  "mcpServers": {
    "jlink-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jlink-mcp"
      ]
    }
  }
}

About this server

J-Link MCP is listed in the Developer Tools category of the MCPNav directory. It is distributed as npm and can be loaded by any client that speaks the Model Context Protocol.

Typical uses include giving your assistant scoped access to the corresponding service so it can answer questions and take actions with real data instead of guessing. Always review what a server can access before you enable it — see our MCP security guide.

Frequently asked questions

What is the J-Link MCP MCP server?

J-Link MCP is an MCP server by Klievan. Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.

How do I install J-Link MCP?

Install it with: npx -y jlink-mcp. Then add the JSON config to your client's MCP settings and restart the client.

Is J-Link MCP free to use?

The MCP server itself is free to install. The source is public on https://github.com/Klievan/jlink-mcp. Any third-party API it calls (such as a search or maps API) may require its own key and billing.

Which clients support J-Link MCP?

Any MCP-compatible client can use it, including Claude Desktop, Cursor, VS Code, Windsurf and custom agents.