arm-migrate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_workloadA | Analyze an LLM workload (Dockerfile, compose file, dependency list, or plain description) for Arm64 migration blockers and optimization opportunities. Returns severity-ranked signals with concrete fixes. |
| generate_migration_planB | Generate ready-to-commit Arm64 migration artifacts: an arm64 Dockerfile (llama.cpp + KleidiAI), a CI benchmark workflow for free GitHub Arm64 runners, build flags, and a migration checklist. |
| trigger_benchmarkA | Trigger the arm-bench workflow (Arm64+KleidiAI vs Arm64 vs x86 benchmark matrix) on a GitHub repo via workflow_dispatch. Requires an authenticated gh CLI; falls back to manual instructions. |
| fetch_benchmark_resultsA | Download artifacts from the latest (or a specific) completed arm-bench run and return the migration report with measured tokens/sec deltas. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: analyze workloads, fetch results, generate migration plans, and trigger benchmarks. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (analyze_workload, fetch_benchmark_results, generate_migration_plan, trigger_benchmark).
With 4 tools, the set covers the core migration workflow without being over- or under-scoped. Each tool earns its place.
The tool surface covers the full migration lifecycle: analyze current workload, benchmark performance, generate migration plan, and trigger benchmarks. No obvious gaps.