What is J-Link-RTT-Viewer-MCP CLAUDE.md?

An instruction file for an MCP server that controls STM32 microcontroller boards through a J-Link debugger. It lets an AI assistant interact with board logs, commands, memory, and firmware as described by the server’s tools.

Connecting to an STM32 board, reading or writing RTT logs, sending commands, resetting the device, reading or writing memory, retrieving device information, and flashing firmware.

It documents the commands, setup, tests, and checks needed to work with the board through the server.

How MisakaMikoto128/J-Link-RTT-Viewer-MCP configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MisakaMikoto128/J-Link-RTT-Viewer-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MisakaMikoto128/J-Link-RTT-Viewer-MCP/master/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/MisakaMikoto128/J-Link-RTT-Viewer-MCP

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/misakamikoto128/j-link-rtt-viewer-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 500 This file is loaded in full into every session.

When invoked 500 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00500	$0.00500
Opus 5	$0.00250	$0.00250
Sonnet 5	$0.00100	$0.00100
Haiku 4.5	$0.00050	$0.00050

Measured 12d ago against content hash 6c8a7b6764a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

J-Link-RTT-Viewer-MCP CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 67 lines

What it actually says

J-Link RTT Viewer MCP Server

MCP server for controlling STM32 boards via J-Link RTT. AI assistants use this to read logs, send commands, and flash firmware through natural language.

Quick Commands

# Install
pip install -r requirements.txt

# Run tests
pytest tests/ -v

# Type check
mypy src/ --ignore-missing-imports

# Lint
ruff check src/

# Start server
python -m src.server

# Test with inspector
npx @modelcontextprotocol/inspector -- python -m src.server

MCP Tools Available

Tool	Key Parameters	What It Does
`connect`	`target="STM32F103C8"`, `interface="SWD"`	Connect to MCU
`disconnect`	-	Disconnect
`read_rtt`	`channels=[0]`	Read RTT logs from MCU
`write_rtt`	`data="freq 200"`	Send command to MCU
`reset`	`mode="normal"`	Reset MCU
`flash_firmware`	`firmware_path="path.hex"`	Flash firmware
`read_memory`	`address=0x08000000, size=256`	Read MCU memory
`write_memory`	`address=0x20000000, data="AABB"`	Write MCU memory
`get_device_info`	-	Get device details

MCU Commands (via write_rtt)

freq <ms>     - Set blink interval (50-5000ms)
mode <on|off|blink> - Set LED mode
status        - Get current settings
ping          - Test connection
reset         - Software reset

Project Structure

src/
  server.py              # MCP server entry
  core/jlink_manager.py  # J-Link hardware interface
tests/                   # 125 tests
target_example/          # STM32 test firmware

Key Technical Details

Uses pylink-square==1.6.0 for J-Link communication
RTT reads use pylink's built-in RTT API
Thread-safe via _run_serialized for J-Link operations
Device names: STM32F103C8 (not STM32F103C8T6)

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 67 lines · 500 tokens per session scan A 6c8a7b6764a1

Subscribe to this mod's changes

J-Link-RTT-Viewer-MCP CLAUDE.md is an instructions file published in the GitHub repository MisakaMikoto128/J-Link-RTT-Viewer-MCP (1 stars, last pushed 2mo ago), licensed MIT. It adds 500 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Hardware and IoT

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

J-Link-RTT-Viewer-MCP: Instructions file for Claude Code