Developer · Remote MCP server
Nodegrove VRAM: can I run it?
Can this LLM run on my GPU? VRAM, speed ceiling and what fits instead, for any model and GPU.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.nodegrove/vram-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- io.nodegrove
- Website
- nodegrove.io/mcp
- Repository
- github.com/nodegrove/vram-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.nodegrove.io/mcp | None |
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @nodegrove/vram-mcp | 1.0.0 | stdio |
How to connect Nodegrove VRAM: can I run it?
Nodegrove VRAM: can I run it? is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nodegrove.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @nodegrove/vram-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @nodegrove/vram-mcp@1.0.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"vram-mcp": {
"command": "npx",
"args": [
"-y",
"@nodegrove/vram-mcp@1.0.0"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Nockchain MCPMoved to io.github.winter0x/nockchain-mcp. This entry is no longer updated. | Local · stdio |
| Node RuntimeThis package is intended for demonstration only. Maintained by JFrog Security. | Local · stdio |
| node9Access control for AI agents and MCP servers: allow, hold for approval, or block each tool call. | Local · stdio |
| NodecelVibe deployment for nodecel — deploy, roll back, diagnose, and manage apps and domains from chat. | Remote · HTTP |
| Nodered MCPMCP server for Node-RED: flows, nodes. Works with any instance. | Local · stdio |
| nodriver — undetected browser automationUndetected anti-bot Chrome automation. 70 tools, parallel isolated browsers. | Local · stdio |
| NoetiveYour agents share what they learn. Semantik finds it by meaning, with no topic names to agree on. | Local · stdio |
| NofaxHuman-in-the-loop approvals and notifications for AI coding agents through a local stdio MCP server. | Local · stdio |