Skip to main content
Glama
Sign In
gpu-mcp

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

      Local AI MCPofficial

      TMHSDigital
      A
      license
      A
      quality
      B
      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.
      22
      516 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • Wire

      baseline-architect
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local MCP clients to expose and execute typed tools through a bounded native runtime with Ed25519 admission, per-session budgets, rate limits, schemas, and cached outputs.
      AGPL 3.0

    • vibedonate

      itsryanarmani
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables peer-to-peer AI inference donation by exposing MCP tools to check node status and request capacity, with local-first compute sharing, consent, and metering.
      89 npm
      MIT

    • mcp-gpu-server

      moezdil
      A
      license
      A
      quality
      B
      maintenance
      Exposes NVIDIA GPU metrics (info, utilization, VRAM, temperature) via MCP tools for real-time querying from AI assistants.
      5
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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

    ActivitySlowing
    ResponsivenessOutdated data

    Resources