Arm Reference

Name: Arm Reference
Author: yerry262

yerry262/arm-reference-mcp·4 plugins

Wire four ARM-focused MCP plugins into Claude Code for register lookup, doc RAG, Graviton-style cloud migration, and TinyML edge deployment.

Overview

arm-reference is a plugin marketplace for the Build phase that bundles four ARM MCP servers totaling dozens of architecture, docs, cloud migration, and TinyML tools.

What is this marketplace?

4 plugins: arm-reference-mcp, arm-docs-rag-mcp, arm-cloud-migration-mcp, arm-tinyml-mcp
arm-reference-mcp: 23 tools (registers, AArch32/AArch64, NEON, SME, barriers, x86 translation)
arm-docs-rag-mcp: 7 tools for manual snippets, errata, encoding, and catalog browse
arm-cloud-migration-mcp: 7 tools (dependency scan, Graviton/Cobalt/Axion/Ampere fit, multi-arch Docker/CI)
arm-tinyml-mcp: 7 tools for edge AI / TinyML deployment analysis
4 plugins in marketplace.json
44 MCP tools named across listings (23 + 7 + 7 + 7)
arm-reference-mcp covers AArch32 and AArch64 reference surfaces

Compatible agents: Claude Code, Cursor, Codex, Windsurf

What problem does it solve?

ARM systems, docs, and arm64 cloud moves are fragmented across manuals and vendor pages, slowing agent-assisted implementation.

Who is it for?

Solo builders shipping firmware, arm64 containers, or Graviton migrations who want MCP-backed ARM expertise in the agent loop.

Skip if: Pure web-only SaaS teams with no ARM surface, beginners who only need high-level app code, or buyers expecting formal certification tooling.

What do I get? / Deliverables

You register one marketplace and expose structured MCP tools so agents answer ARM questions, plan migrations, and reason about edge models with less hallucination.

Up to four ARM MCP servers registered from one marketplace
Agent-callable reference, doc search, migration, and TinyML tool groups
Repeatable arm64 CI/Docker guidance from migration MCP workflows

Plugins in this marketplace

4 plugins — install individually after you add the marketplace.

PluginVersion

Arm Reference McpARM architecture reference -- 23 tools covering registers, instructions, calling conventions, exception levels, security models, page tables, memory attributes, extensions, assembly patterns, barriers, core/IP reference, NEON intrinsics, SME tiles, optimization, system registers, PMU events, and x86-to-ARM translation for AArch32 and AArch64.—Arm Docs Rag McpARM documentation RAG -- 7 tools for searching curated ARM manual snippets, explaining architecture concepts, locating register documentation, retrieving core errata, comparing features across architecture versions, browsing documentation catalogs, and instruction encoding reference.—Arm Cloud Migration McpARM cloud migration advisor -- 7 tools for scanning x86 dependencies, recommending ARM cloud instances (AWS Graviton, Azure Cobalt, GCP Axion, Oracle Ampere), checking Docker arm64 support, generating cross-arch CI configs, estimating migration effort, generating multi-arch Dockerfiles, and comparing ARM vs x86 performance.—Arm Tinyml McpARM TinyML / edge AI deployment -- 7 tools for analyzing model operator compatibility (Ethos-U, CMSIS-NN, ARM NN), recommending quantization strategies, estimating inference performance, generating deployment code, comparing edge targets, suggesting model architectures for hardware constraints, and explaining TinyML frameworks.—

Recommended Marketplaces

Ably Agent Skillsably/agent-skills

1 plugins1 stars

Bgreenwell Pluginsbgreenwell/claude-plugins

2 plugins1 stars

Bingx Ai SkillsBingX-API/api-ai-skills

1 plugins13 stars

Boar Networkboar-network/blockchain-mcp

1 plugins12 stars

Cc SwitchHuaer02/cc-switch

1 plugins

Cellwhispererepigen/CellWhisperer

1 plugins208 stars

Journey fit

Primary fit

BuildIntegrations & version control

Build integrations is the primary shelf because the value is MCP tool surfaces agents call while writing firmware, containers, or migration plans. MCP servers are agent integrations—not standalone apps—so they belong under integrations even when they inform ship-time CI or operate-time tuning.

How it compares

Multi-plugin MCP reference suite for ARM, not a single Claude skill or a general-purpose dev marketplace.

Common Questions / FAQ

Who is Arm Reference for?

It is for developers and indie infra hackers working on ARM architecture, arm64 cloud instances, or TinyML edge targets who want MCP tools in Claude Code.

When should I use Arm Reference?

Use it while integrating low-level ARM code, preparing multi-arch Docker/CI, or evaluating AWS Graviton and similar platforms during build and ship planning.

How do I add Arm Reference to my agent?

Add the yerry262 marketplace in Claude Code, enable the MCP plugins you need, and configure each server per its repo README before invoking tools in sessions.