Skip to main content
Glama
CisnerosCodes

arm-migrate-mcp

by CisnerosCodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to arm-migrate-mcp

No user-submitted related servers found.

    Related Servers

    • arm-code-mcp

      jean-johnson-zwix
      A
      license
      A
      quality
      D
      maintenance
      Helps AI assistants optimize Linux workloads on Arm64 by parsing perf report output, recommending NEON SIMD intrinsics for hot loops, and auditing Python dependency manifests for arm64 wheel availability — all offline and structured.
      4
      Apache 2.0

    • InferBench

      RudrenduPaul
      A
      license
      Not graded
      quality
      A
      maintenance
      Vendor-neutral local LLM inference benchmark and hardware-config advisor for mlx and llama.cpp. Exposes an MCP tool that measures real tokens/second on your own hardware.
      15 npm
      Apache 2.0
    • Arm MCP Server by arm

      Arm MCP Serverofficial

      arm
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants with tools for Arm architecture development, migration, and optimization, including knowledge base search, code migration analysis, container inspection, assembly performance analysis, and workload performance testing.
      91
      Apache 2.0

    • chimeraforge

      Sahil170595
      A
      license
      A
      quality
      A
      maintenance
      LLM deployment planner: given a model and a GPU, answers will it fit, will it hit your SLO, and what will it cost. Sizes VRAM and KV-cache from the model's real architecture, and labels every number measured, estimated, or unknown.
      5
      735 PyPI
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: analyze workloads, fetch results, generate migration plans, and trigger benchmarks. No overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (analyze_workload, fetch_benchmark_results, generate_migration_plan, trigger_benchmark).

    Tool Count5/5

    With 4 tools, the set covers the core migration workflow without being over- or under-scoped. Each tool earns its place.

    Completeness5/5

    The tool surface covers the full migration lifecycle: analyze current workload, benchmark performance, generate migration plan, and trigger benchmarks. No obvious gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources