computegpu_get_started — computegpu MCP Tool
computegpu_get_started
(computegpu get started) is one of 2 tools on the
computegpu
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call computegpu_get_started from your client
- Claude Code computegpu computegpu_get_started run in your project directory
- Claude Desktop computegpu computegpu_get_started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor computegpu computegpu_get_started ~/.cursor/mcp.json
- VS Code computegpu computegpu_get_started .vscode/mcp.json
- Zed computegpu computegpu_get_started ~/.config/zed/settings.json
- Windsurf computegpu computegpu_get_started ~/.codeium/windsurf/mcp_config.json
- Cline computegpu computegpu_get_started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI computegpu computegpu_get_started ~/.gemini/settings.json
- Grok computegpu computegpu_get_started .mcp.json (in your project root)
- ChatGPT computegpu computegpu_get_started Settings → Connectors → Advanced → Developer mode
- Claude.ai computegpu computegpu_get_started Settings → Connectors → Add custom connector
- LangChain computegpu computegpu_get_started pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http computegpu https://mcp.computegpu.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.