Skip to content
Back to search

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.

Checked today

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
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/arm--mcp/badge.svg)](/listings/arm--mcp)

HTML

<a href="/listings/arm--mcp"><img src="/api/listings/arm--mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

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.

  1. [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/arm/mcp/badge)](https://scorecard.dev/viewer/?uri=github.com/arm/mcp)
  2. [![SLSA Build Level 3](https://slsa.dev/images/gh-badge-level3.svg)](docs/slsa-build-level-3.md)
  3. # Arm MCP Server
  4. An [MCP](https://modelcontextprotocol.io/) server providing AI assistants with tools and knowledge for Arm architecture development, migration, and optimization.
  5. ## Using the Arm MCP Server
  6. If your goal is to migrate an application from x86 to Arm as quickly as possible, start here:
  7. [Automate x86-to-Arm application migration using Arm MCP Server](https://learn.arm.com/learning-paths/servers-and-cloud-computing/arm-mcp-server/)
  8. ## Features
  9. This MCP server equips AI assistants with specialized tools for Arm development:
  10. - **[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
  11. - **Code Migration Analysis**: Scan codebases for Arm compatibility using [migrate-ease](https://github.com/migrate-ease/migrate-ease) (supports C++, Python, Go, JavaScript, Java)
  12. - **Container Architecture Inspection**: Check Docker image architecture support using integrated [Skopeo](https://github.com/containers/skopeo) and check-image tools.
  13. - **Assembly Performance Analysis**: Analyze assembly code performance using LLVM-MCA
  14. ## Pre-Built Image
  15. 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`
  16. ## Prerequisites
  17. - Docker with Buildx support
  18. - An MCP-compatible AI assistant client (e.g. GitHub Copilot, Kiro CLI, Codex CLI, Claude Code, etc)
  19. ## Quick Start
  20. ### 1. Build the Docker Image
  21. From the root of this repository:
  22. ```bash
  23. docker buildx build -f mcp-local/Dockerfile -t armlimited/arm-mcp . --load
  24. ```
  25. This builds for the Docker host's native architecture. The release workflow is
  26. responsible for explicit multi-architecture builds.
  27. For local development builds, see the
  28. [Quick Local Development Builds section in CONTRIBUTING.md](CONTRIBUTING.md#quick-local-development-builds).
  29. ### 2. Configure Your MCP Client
  30. Choose the configuration that matches your MCP client:
  31. #### Claude Code
  32. Add to `.mcp.json` in your project:
  33. ```json
  34. {
  35. "mcpServers": {
  36. "arm-mcp": {
  37. "command": "docker",
  38. "args": [
  39. "run",
  40. "--rm",
  41. "-i",
  42. "--pull=always",
  43. "-v", "/path/to/your/workspace:/workspace",
  44. "armlimited/arm-mcp"
  45. ]
  46. }
  47. }
  48. }
  49. ```
  50. #### GitHub Copilot (VS Code)
  51. Add to `.vscode/mcp.json` in your project, or globally at `~/Library/Application Support/Code/User/mcp.json` (macOS):
  52. ```json
  53. {
  54. "servers": {
  55. "arm-mcp": {
  56. "type": "stdio",
  57. "command": "docker",
  58. "args": [
  59. "run",
  60. "--rm",
  61. "-i",
  62. "--pull=always",
  63. "-v", "/path/to/your/workspace:/workspace",
  64. "armlimited/arm-mcp"
  65. ]
  66. }
  67. }
  68. }
  69. ```
  70. The easiest way to open this file in VS Code for editing is command+shift+p and search for
  71. MCP: Open User Configuration
  72. #### AWS Kiro CLI
  73. Add to `~/.kiro/settings/mcp.json`:
  74. ```json
  75. {
  76. "mcpServers": {
  77. "arm-mcp": {
  78. "command": "docker",
  79. "args": [
  80. "run",
  81. "--rm",
  82. "-i",
  83. "--pull=always",
  84. "-v", "/path/to/your/workspace:/workspace",
  85. "armlimited/arm-mcp"
  86. ],
  87. "timeout": 60000
  88. }
  89. }
  90. }
  91. ```
  92. #### Gemini CLI
  93. It is recommended to use a project-local configuration file to ensure the relevant workspace is mounted.
  94. Add to `.gemini/settings.json` in your project root:
  95. ```json
  96. {
  97. "mcpServers": {
  98. "arm-mcp": {
  99. "command": "docker",
  100. "args": [
  101. "run",
  102. "--rm",
  103. "-i",
  104. "--pull=always",
  105. "-v", "/path/to/your/workspace:/workspace",
  106. "armlimited/arm-mcp"
  107. ]
  108. }
  109. }
  110. }
  111. ```
  112. #### MCP Clients using TOML format (e.g. Codex CLI)
  113. ```toml
  114. [mcp_servers.arm-mcp]
  115. command = "docker"
  116. args = [
  117. "run",
  118. "--rm",
  119. "-i",
  120. "--pull=always",
  121. "-v", "/path/to/your/workspace:/workspace",
  122. "armlimited/arm-mcp"
  123. ]
  124. ```
  125. **Note**: Replace `/path/to/your/workspace` with the actual path to your project directory that you want the MCP server to access.
  126. ### 3. Restart Your MCP Client
  127. After updating the configuration, restart your MCP client to load the Arm MCP server.
  128. ## Knowledge-base search
  129. `knowledge_base_search` returns up to five ranked chunks by default. Optional settings:
  130. - `k`: an integer from 1 to 20 limiting initial matches, defaulting to 5 when omitted.
  131. Explicit `null` and values outside this range are rejected.
  132. - `filters`: `doc_type`, `product`, `platform`, or `edition`, each accepting a
  133. label or non-empty list. Values within a field use OR; fields use AND.
  134. Matching ignores case and surrounding whitespace. Use known metadata labels;
  135. records with missing tags cannot match a filter.
  136. ```json
  137. {"query": "How do SVE predicated loads work?", "filters": {"doc_type": "Intrinsic", "product": "SVE"}, "k": 3}
  138. ```
  139. Choose `scope` for the amount of context:
  140. | Scope | Content returned |
  141. | --- | --- |
  142. | `chunks` (default) | Ranked matching chunks. |
  143. | `page` | All stored chunks from each matched page, in order. |
  144. Page expansion returns shared pages once. Filters and `k` select initial matches;
  145. they do not limit expanded content. Use expansion only when the user requests
  146. wider context, since responses can be large. No live pages are fetched.
  147. Expansion requires regenerated KB artifacts with complete ordering metadata;
  148. missing or conflicting context returns an error. The shared search library retains
  149. `parent_resource`; it is temporarily disabled in MCP pending further evaluation.
  150. See the [shared search documentation](arm_kb_search/README.md) for API and metadata details.
  151. ## Logging
  152. Depending on usage, the server may write two log files under `/workspace`. With the
  153. configuration examples above, these files appear in the project directory on
  154. your computer:
  155. - `mcp-traffic.jsonl` records when tools are used, the inputs provided, and the
  156. reason for each tool call. It also records results from knowledge base
  157. searches.
  158. - `error_logging.yaml` records details about errors encountered by the server.
  159. This information can help with troubleshooting.
  160. These logs may contain information from your project and tool requests. Review
  161. their contents before sharing them.
  162. ## Development and contributing
  163. See [CONTRIBUTING.md](CONTRIBUTING.md) for repository structure, integration
  164. testing, reproducible build inputs, runtime-egress validation, dependency
  165. updates, and release workflows.
  166. ## Troubleshooting
  167. ### Accessing the Container Shell
  168. To debug or explore the container environment:
  169. ```bash
  170. docker run --rm -it --entrypoint /bin/bash armlimited/arm-mcp
  171. ```
  172. ### Common Issues
  173. - **Timeout errors during migration scans**: Increase the `timeout` value in your MCP client configuration (e.g., `"timeout": 120000` for 2 minutes)
  174. - **Empty workspace**: Ensure your volume mount path is correct and the directory exists
  175. - **Architecture mismatches**: Confirm that the local image matches the Docker host's native architecture; use the release workflow for explicit cross-platform builds.
  176. 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).
  177. ## License
  178. Copyright © 2026, Arm Limited and Contributors. All rights reserved.
  179. Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for details.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.