Official Arm MCP server for code migration, optimization, and Arm architecture guidance
io.github.arm/arm-mcp — Model Context Protocol Server
The io.github.arm/arm-mcp server is an official MCP server for providing AI assistants with tools and knowledge focused on Arm architecture development. It supports code migration, optimization, and architecture guidance, with documentation describing how to use it for x86-to-Arm application migration.
🛠️ Key Features
Official Arm MCP server for AI assistants
Tools and knowledge for Arm architecture development
Code migration support
Optimization guidance
Arm architecture guidance
🚀 Use Cases
Migrating applications from x86 to Arm as quickly as possible
Automating x86-to-Arm application migration
⚠️ Limitations
The available source data does not list specific tools, tool counts, or topics beyond the stated focus areas.
📚 Additional Metadata
OpenSSF Scorecard badge is referenced for github.com/arm/mcp
SLSA Build Level 3 badge is referenced (docs/slsa-build-level-3.md)
Topics, toolCount, and extended readme details are not provided in the source material.
This MCP server equips AI assistants with specialized tools for Arm development:
Knowledge Base Search: Keyword and semantic search across Arm documentation, learning resources, intrinsics, and software compatibility information, with technical-name aliases
Code Migration Analysis: Scan codebases for Arm compatibility using migrate-ease (supports C++, Python, Go, JavaScript, Java)
Container Architecture Inspection: Check Docker image architecture support using integrated Skopeo and check-image tools.
Assembly Performance Analysis: Analyze assembly code performance using LLVM-MCA
Pre-Built Image
If you would prefer to use a pre-built, multi-arch image, the official image can be found in Docker Hub here: armlimited/arm-mcp:latest
Prerequisites
Docker with Buildx support
An MCP-compatible AI assistant client (e.g. GitHub Copilot, Kiro CLI, Codex CLI, Claude Code, etc)
Note: Replace /path/to/your/workspace with the actual path to your project directory that you want the MCP server to access.
3. Restart Your MCP Client
After updating the configuration, restart your MCP client to load the Arm MCP server.
Knowledge-base search
knowledge_base_search returns up to five ranked chunks by default. Optional settings:
k: an integer from 1 to 20 limiting initial matches, defaulting to 5 when omitted.
Explicit null and values outside this range are rejected.
filters: doc_type, product, platform, or edition, each accepting a
label or non-empty list. Values within a field use OR; fields use AND.
Matching ignores case and surrounding whitespace. Use known metadata labels;
records with missing tags cannot match a filter.
json
{"query":"How do SVE predicated loads work?","filters":{"doc_type":"Intrinsic","product":"SVE"},"k":3}
Choose scope for the amount of context:
Scope
Content returned
chunks (default)
Ranked matching chunks.
page
All stored chunks from each matched page, in order.
Page expansion returns shared pages once. Filters and k select initial matches;
they do not limit expanded content. Use expansion only when the user requests
wider context, since responses can be large. No live pages are fetched.
Expansion requires regenerated KB artifacts with complete ordering metadata;
missing or conflicting context returns an error. The shared search library retains
parent_resource; it is temporarily disabled in MCP pending further evaluation.
See the shared search documentation for API and metadata details.
Logging
Depending on usage, the server may write two log files under /workspace. With the
configuration examples above, these files appear in the project directory on
your computer:
mcp-traffic.jsonl records when tools are used, the inputs provided, and the
reason for each tool call. It also records results from knowledge base
searches.
error_logging.yaml records details about errors encountered by the server.
This information can help with troubleshooting.
These logs may contain information from your project and tool requests. Review
their contents before sharing them.
Development and contributing
See CONTRIBUTING.md for repository structure, integration
testing, reproducible build inputs, runtime-egress validation, dependency
updates, and release workflows.
Troubleshooting
Accessing the Container Shell
To debug or explore the container environment:
bash
docker run --rm -it --entrypoint /bin/bash armlimited/arm-mcp
Common Issues
Timeout errors during migration scans: Increase the timeout value in your MCP client configuration (e.g., "timeout": 120000 for 2 minutes)
Empty workspace: Ensure your volume mount path is correct and the directory exists
Architecture mismatches: Confirm that the local image matches the Docker host's native architecture; use the release workflow for explicit cross-platform builds.