Koskamo

Nodegrove VRAM MCP MCP server

An official MCP server by Nodegrove that allows AI assistants to determine if specific LLMs fit on a user's GPU. It provides VRAM estimates, speed ceilings, and alternative model recommendations based on Nodegrove's arithmetic formulas, supporting both known GPUs and Hugging Face repositories.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Nodegrove
MCP endpoint (Streamable HTTP)
https://mcp.nodegrove.io/mcp
Vendor documentation

What you can do with it

  • Check if a specific LLM fits on a GPU with given context length
  • Find the best model for a specific GPU memory capacity
  • Estimate VRAM requirements for models from Hugging Face repos
  • List supported models and GPUs with their specifications
Tools advertised by the last live check:
  • can_i_run
  • what_fits
  • estimate_vram
  • estimate_from_hf_repo
  • list_models
  • list_gpus

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http nodegrove-vram-mcp https://mcp.nodegrove.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add nodegrove-vram-mcp --url https://mcp.nodegrove.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable nodegrove-vram-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "nodegrove-vram-mcp": {
      "url": "https://mcp.nodegrove.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "nodegrove-vram-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.nodegrove.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start nodegrove-vram-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "nodegrove-vram-mcp": {
      "type": "http",
      "url": "https://mcp.nodegrove.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http nodegrove-vram-mcp https://mcp.nodegrove.io/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "nodegrove-vram-mcp": {
      "url": "https://mcp.nodegrove.io/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "nodegrove-vram-mcp": {
      "serverUrl": "https://mcp.nodegrove.io/mcp"
    }
  }
}

Do you run Nodegrove VRAM MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing