mcp
Arm's MCP server
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/arm/mcp with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/arm/mcp'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/arm--mcp)HTML
<a href="/listings/arm--mcp"><img src="/api/listings/arm--mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
1. Build the Docker Image
From the root of this repository:
docker buildx build -f mcp-local/Dockerfile -t armlimited/arm-mcp . --load
This builds for the Docker host's native architecture. The release workflow is responsible for explicit multi-architecture builds.
2. Configure Your MCP Client
Choose the configuration that matches your MCP client:
Claude Code
Add to `.mcp.json` in your project:
{
"mcpServers": {
"arm-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--pull=always",
"-v", "/path/to/your/workspace:/workspace",
"armlimited/arm-mcp"
]
}
}
}GitHub Copilot (VS Code)
Add to `.vscode/mcp.json` in your project, or globally at `~/Library/Application Support/Code/User/mcp.json` (macOS):
{
"servers": {
"arm-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--pull=always",
"-v", "/path/to/your/workspace:/workspace",
"armlimited/arm-mcp"
]
}
}
}The easiest way to open this file in VS Code for editing is command+shift+p and search for
MCP: Open User Configuration
AWS Kiro CLI
Add to `~/.kiro/settings/mcp.json`:
{
"mcpServers": {
"arm-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--pull=always",
"-v", "/path/to/your/workspace:/workspace",
"armlimited/arm-mcp"
],
"timeout": 60000
}
}
}Gemini CLI
It is recommended to use a project-local configuration file to ensure the relevant workspace is mounted.
Add to `.gemini/settings.json` in your project root:
{
"mcpServers": {
"arm-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"--pull=always",
"-v", "/path/to/your/workspace:/workspace",
"armlimited/arm-mcp"
]
}
}
}MCP Clients using TOML format (e.g. Codex CLI)
[mcp_servers.arm-mcp] command = "docker" args = [ "run", "--rm", "-i", "--pull=always", "-v", "/path/to/your/workspace:/workspace", "armlimited/arm-mcp" ]
**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.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 243 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- [](https://scorecard.dev/viewer/?uri=github.com/arm/mcp)
- [](docs/slsa-build-level-3.md)
- # Arm MCP Server
- An [MCP](https://modelcontextprotocol.io/) server providing AI assistants with tools and knowledge for Arm architecture development, migration, and optimization.
- ## Using the Arm MCP Server
- If your goal is to migrate an application from x86 to Arm as quickly as possible, start here:
- [Automate x86-to-Arm application migration using Arm MCP Server](https://learn.arm.com/learning-paths/servers-and-cloud-computing/arm-mcp-server/)
- ## Features
- This MCP server equips AI assistants with specialized tools for Arm development:
- - **[Knowledge Base Search](arm_kb_search/README.md)**: 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](https://github.com/migrate-ease/migrate-ease) (supports C++, Python, Go, JavaScript, Java)
- - **Container Architecture Inspection**: Check Docker image architecture support using integrated [Skopeo](https://github.com/containers/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)
- ## Quick Start
- ### 1. Build the Docker Image
- From the root of this repository:
- ```bash
- docker buildx build -f mcp-local/Dockerfile -t armlimited/arm-mcp . --load
- ```
- This builds for the Docker host's native architecture. The release workflow is
- responsible for explicit multi-architecture builds.
- For local development builds, see the
- [Quick Local Development Builds section in CONTRIBUTING.md](CONTRIBUTING.md#quick-local-development-builds).
- ### 2. Configure Your MCP Client
- Choose the configuration that matches your MCP client:
- #### Claude Code
- Add to `.mcp.json` in your project:
- ```json
- {
- "mcpServers": {
- "arm-mcp": {
- "command": "docker",
- "args": [
- "run",
- "--rm",
- "-i",
- "--pull=always",
- "-v", "/path/to/your/workspace:/workspace",
- "armlimited/arm-mcp"
- ]
- }
- }
- }
- ```
- #### GitHub Copilot (VS Code)
- Add to `.vscode/mcp.json` in your project, or globally at `~/Library/Application Support/Code/User/mcp.json` (macOS):
- ```json
- {
- "servers": {
- "arm-mcp": {
- "type": "stdio",
- "command": "docker",
- "args": [
- "run",
- "--rm",
- "-i",
- "--pull=always",
- "-v", "/path/to/your/workspace:/workspace",
- "armlimited/arm-mcp"
- ]
- }
- }
- }
- ```
- The easiest way to open this file in VS Code for editing is command+shift+p and search for
- MCP: Open User Configuration
- #### AWS Kiro CLI
- Add to `~/.kiro/settings/mcp.json`:
- ```json
- {
- "mcpServers": {
- "arm-mcp": {
- "command": "docker",
- "args": [
- "run",
- "--rm",
- "-i",
- "--pull=always",
- "-v", "/path/to/your/workspace:/workspace",
- "armlimited/arm-mcp"
- ],
- "timeout": 60000
- }
- }
- }
- ```
- #### Gemini CLI
- It is recommended to use a project-local configuration file to ensure the relevant workspace is mounted.
- Add to `.gemini/settings.json` in your project root:
- ```json
- {
- "mcpServers": {
- "arm-mcp": {
- "command": "docker",
- "args": [
- "run",
- "--rm",
- "-i",
- "--pull=always",
- "-v", "/path/to/your/workspace:/workspace",
- "armlimited/arm-mcp"
- ]
- }
- }
- }
- ```
- #### MCP Clients using TOML format (e.g. Codex CLI)
- ```toml
- [mcp_servers.arm-mcp]
- command = "docker"
- args = [
- "run",
- "--rm",
- "-i",
- "--pull=always",
- "-v", "/path/to/your/workspace:/workspace",
- "armlimited/arm-mcp"
- ]
- ```
- **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](arm_kb_search/README.md) 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](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.
- Suspected vulnerabilities must not be reported in public issues. See the [Arm MCP security policy](https://github.com/arm/mcp/security/policy) and report them via [Arm PSIRT](https://developer.arm.com/support/arm-security-updates/report-security-vulnerabilities).
- ## License
- Copyright © 2026, Arm Limited and Contributors. All rights reserved.
- Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for details.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.