Kubernetes GPU orchestration — NVIDIA device plugin — Aguasto Research MCP Resource
Kubernetes GPU orchestration — NVIDIA device plugin
is one of 90 resources on the
Aguasto Research
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Kubernetes GPU orchestration — NVIDIA device plugin from your client
- Claude Code Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin run in your project directory
- Claude Desktop Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/.cursor/mcp.json
- VS Code Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin .vscode/mcp.json
- Zed Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/.config/zed/settings.json
- Windsurf Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/.codeium/windsurf/mcp_config.json
- Cline Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin ~/.gemini/settings.json
- Grok Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin .mcp.json (in your project root)
- ChatGPT Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin Settings → Connectors → Advanced → Developer mode
- Claude.ai Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin Settings → Connectors → Add custom connector
- LangChain Aguasto Research Resource/Kubernetes GPU orchestration — NVIDIA device plugin pip install langchain-mcp-adapters
Other resources on this server
- API Versioning & Deprecation Policy
- Developer Sandbox & Synthetic API Tests
- Aguasto | Modular AI Infrastructure, GPU Compute & Inference
- Infrastructure
- GPU Cloud
- AI Inference
- Development & Investment
- Company
- Contact
- Privacy
- Public Research Terms of Use
- AI Compute Research Topics
- GPU systems & local clusters
- Model serving & inference
- Modular infrastructure & resources
- Compute economics & evidence
- AI Compute & Infrastructure Glossary
- Research Sources & Methodologies
- Developer API, MCP & SDK Documentation
- Aguasto Research & Resources
- GPU Library
- Model Index
- Inference Stack Library
- AI Infrastructure Engineering Guides
- AI Infrastructure Insights
- AI Infrastructure Research
- Public Infrastructure Case Analyses
- Why Modular AI Data Centers?
- Cooling & Resource Efficiency
- OEM & Strategic Collaboration
- Compare GPU & Rack References
- Compare Open-Weight Model References
- AI Infrastructure Engineering Calculators
- The Growing Friction in Hyperscale Data Center Development
- NVIDIA H100 SXM
- NVIDIA H200 SXM
- NVIDIA B200 SXM
- NVIDIA B300
- NVIDIA GB200 NVL72
- NVIDIA GB300 NVL72
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.