Skip to main content
Glama
MYaelMendez

gpu-mcp

by MYaelMendez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to gpu-mcp

No user-submitted related servers found.

    Related Servers

    • Local AI MCP by TMHSDigital

      Local AI MCPofficial

      TMHSDigital
      A
      license
      A
      quality
      A
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      16
      18 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • prism

      senssei
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local AI models to be used through MCP, exposing tools for coding assistance, code review, model listing, status checks, and benchmarking.
      230 PyPI
      Apache 2.0

    • devbench

      jrlinjr
      A
      license
      A
      quality
      C
      maintenance
      A local developer workbench that exposes MCP tools, resources, and prompts for AI-driven development workflows, running entirely on a single GPU with Ollama.
      4
      MIT

    • McpApp

      krok1029
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local-first MCP server for AI-native software delivery, enabling structured specifications, human approval gates, controlled repository operations, verification evidence, review, and traceability.
      Apache 2.0
    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

    A3.5/5.0

    Scored across 5 tools

    Disambiguation3/5

    The GPU tools (compile_kernel, run_kernel, probe_gpu) are distinct from the Rust/WASM tools (rust_build_wasm, rust_run_wasm), but the mixing of two unrelated domains under the 'gpu-mcp' name creates confusion about which tool to use for a given task.

    Naming Consistency4/5

    All tools follow a verb_noun pattern (e.g., compile_kernel, probe_gpu), but the Rust tools include a 'rust_' prefix while the GPU tools do not, introducing a minor inconsistency.

    Tool Count5/5

    With only 5 tools, the number is well-suited for a focused MCP server. Each tool serves a specific purpose without unnecessary redundancy.

    Completeness3/5

    The GPU toolset covers compilation, execution, and monitoring, but lacks features like device management or memory operations. The Rust/WASM subset is minimal and feels like an afterthought, leaving both domains incomplete.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources