Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Official Arm MCP server for code migration, optimization, and Arm architecture guidance
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"arm": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/armlimited/arm-mcp:2.4.0"
]
}
}
}Run this in your terminal
claude mcp add arm -- docker run -i --rm docker.io/armlimited/arm-mcp:2.4.0Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"arm": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/armlimited/arm-mcp:2.4.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"arm": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"docker.io/armlimited/arm-mcp:2.4.0"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account arm, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.4.0) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server providing AI assistants with tools and knowledge for Arm architecture development, migration, and optimization.
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
This MCP server equips AI assistants with specialized tools for Arm development:
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
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.
For local development builds, see the Quick Local Development Builds section in CONTRIBUTING.md.
Choose the configuration that matches your MCP client:
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" ] } } }
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
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 } } }
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_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.
After updating the configuration, restart your MCP client to load the Arm MCP server.
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.
See CONTRIBUTING.md for repository structure, integration testing, reproducible build inputs, runtime-egress validation, dependency updates, and release workflows.
To debug or explore the container environment:
docker run --rm -it --entrypoint /bin/bash armlimited/arm-mcp
timeout value in your MCP client configuration (e.g., "timeout": 120000 for 2 minutes)Suspected vulnerabilities must not be reported in public issues. See the Arm MCP security policy and report them via Arm PSIRT.
Copyright © 2026, Arm Limited and Contributors. All rights reserved.
Licensed under the Apache License, Version 2.0. See LICENSE for details.