GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
MCP server for Arm64 Linux performance: parse perf output, suggest NEON intrinsics, audit deps.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
ARM_CODE_MCP_LOG_LEVEL你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"arm-code": {
"command": "uvx",
"args": [
"arm-code-mcp"
],
"env": {
"ARM_CODE_MCP_LOG_LEVEL": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add arm-code --env ARM_CODE_MCP_LOG_LEVEL=your-value -- uvx arm-code-mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"arm-code": {
"command": "uvx",
"args": [
"arm-code-mcp"
],
"env": {
"ARM_CODE_MCP_LOG_LEVEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"arm-code": {
"type": "stdio",
"command": "uvx",
"args": [
"arm-code-mcp"
],
"env": {
"ARM_CODE_MCP_LOG_LEVEL": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
ARM_CODE_MCP_LOG_LEVEL env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 jean-johnson-zwix 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于6个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server that helps AI assistants optimize Linux workloads on Arm64. It parses perf report output, recommends NEON SIMD intrinsics for hot loops, and audits Python dependency manifests for arm64 wheel availability — all offline, all structured, all callable from Claude Code, GitHub Copilot, and Codex.
perf report --stdio into a ranked list of hot symbolsrequirements.txt, pyproject.toml, or Dockerfile that lack arm64 wheels or require special handlingdocker pull jeannjohnson/arm-code-mcp:latest
Add to your MCP client config (e.g. ~/.claude/mcp.json):
{
"mcpServers": { "arm-code-mcp": { "command": "docker", "args": ["run", "--rm", "-i", "jeannjohnson/arm-code-mcp:latest"] } } }
Restart your client. All three tools are now available.
analyze_perf_outputParse raw perf report --stdio output and return the top hot symbols, ranked by overhead.
analyze_perf_output(
perf_report_text: str, # raw stdout of perf report --stdio top_n: int = 10, # max symbols to return min_overhead_pct: float = 0.5, # ignore symbols below this % ) -> dict
Example response:
{
"summary": { "total_samples": 5432100, "total_events": null, "command": "myapp" }, "hot_symbols": [ {"overhead_pct": 24.17, "samples": 1245, "command": "myapp", "module": "myapp", "symbol": "process_buffer"}, {"overhead_pct": 12.34, "samples": 636, "command": "myapp", "module": "libc-2.31.so", "symbol": "__memcpy_avx_unaligned_erms"} ], "warnings": [] }
suggest_neon_intrinsicRecommend NEON intrinsics for a hot loop using hybrid semantic + exact-name retrieval over a curated knowledge base of 110 intrinsics.
suggest_neon_intrinsic(
operation_description: str, # e.g. "32-bit float multiply-accumulate" target_arch: str = "armv8-a", # "armv8-a" | "armv8.2-a" | "armv9-a" top_k: int = 5, ) -> dict
Example response:
{
"matches": [ { "intrinsic": "vmlaq_f32", "signature": "float32x4_t vmlaq_f32(float32x4_t a, float32x4_t b, float32x4_t c)", "header": " ", "min_arch": "armv8-a", "description": "Multiply-accumulate: a + (b * c), lane-wise, 4x f32.", "score": 0.9142 } ], "notes": "Filtered to armv8-a. KB contains 110 entries (103 compatible)." }
check_arm64_depsScan a dependency manifest and flag packages with known arm64 compatibility issues. Fully offline — no network calls, fast, deterministic.
check_arm64_deps(
file_content: str, # raw text of the manifest file_type: str = "requirements.txt", # "requirements.txt" | "pyproject.toml" | "Dockerfile" ) -> dict
Example response:
{
"checked": ["numpy", "tensorflow", "cupy-cuda12x", "faiss-cpu", "requests"], "issues": [ {"package": "cupy-cuda12x", "severity": "error", "message": "GPU-only package with no arm64 wheel. Use cupy with ROCm or a CPU fallback."}, {"package": "tensorflow", "severity": "warning", "message": "Official TensorFlow PyPI wheels are x86-only before 2.10; use tensorflow-aarch64 or build from source."}, {"package": "faiss-cpu", "severity": "warning", "message": "No official arm64 wheel on PyPI; build from source or use the conda-forge package."}, {"package": "numpy", "severity": "info", "message": "arm64 wheels available from PyPI since 1.21.0. Ensure version >= 1.21.0."} ], "summary": "Checked 5 package(s): 1 error(s), 2 warning(s), 1 info(s)." }
Severity levels:
| Level | Meaning |
|---|---|
error | No arm64 wheel exists (e.g. GPU-only packages) |
warning | Wheel exists but requires a workaround or alternative source |
info | Wheel available; version constraint or system-lib note applies |
All env vars are optional. The server works with no configuration.
| Variable | Default | Description |
|---|---|---|
ARM_CODE_MCP_LOG_LEVEL | INFO | Log verbosity: DEBUG, INFO, WARNING |
ARM_CODE_MCP_KB_PATH | bundled JSONL | Override path to neon_intrinsics.jsonl |
ARM_CODE_MCP_CACHE_DIR | ~/.cache/arm-code-mcp | Embedding cache directory |
Pass env vars to the container:
docker run --rm -i \
-e ARM_CODE_MCP_LOG_LEVEL=DEBUG \ jeannjohnson/arm-code-mcp:latest
suggest_neon_intrinsic is evaluated against 15 hand-curated (query, expected intrinsic) pairs using the real all-MiniLM-L6-v2 embedding model. Current baseline:
| Metric | Score |
|---|---|
| hit@1 | 0.667 |
| hit@3 | 0.933 |
| hit@5 | 1.000 |
| MRR | 0.817 |
The regression guard exits non-zero if hit@3 drops below 0.70.
Run the eval harness locally:
uv sync
make eval
See eval/README.md for methodology and known limitations.
git clone https://github.com/jean-johnson-zwix/arm-code-mcp
cd arm-code-mcp uv sync make test # 78 tests make lint # ruff check + format make eval # real model, 15 gold queries
Makefile targets:
| Target | Description |
|---|---|
make setup | uv sync + pre-commit install |
make test | Run the full test suite |
make lint | ruff check + ruff format --check |
make eval | Run the NEON retrieval eval harness |
make docker-build | Build arm-code-mcp:dev locally |
make docker-run | Run the local dev image over stdio |
Multi-arch images (linux/amd64 + linux/arm64) are built and pushed automatically by .github/workflows/release.yml on v*.*.* tags.
The NEON intrinsics knowledge base lives in src/arm_code_mcp/kb/data/neon_intrinsics.jsonl (110 entries). To add intrinsics or refresh after a model upgrade, see docs/kb-refresh.md.
Tools
parse_flamegraph — extract hot paths from Linux perf flamegraph SVGsuggest_sve2_intrinsic — extend retrieval to SVE2 intrinsics (Neoverse V2, Cortex-X4)Eval
Coming soon.
Stars, forks, and issues are welcome. Open a PR or file an issue on GitHub.
Good first issues:
kb/data/neon_intrinsics.jsonlparse_flamegraph tool for Linux perf flamegraph SVG filesApache 2.0 — same as arm/mcp.