gpu_index — corpusAI Cloud Pricing MCP Tool
gpu_index
(gpu index) is one of 35 tools on the
corpusAI Cloud Pricing
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gpu_index from your client
- Claude Code corpusAI Cloud Pricing gpu_index run in your project directory
- Claude Desktop corpusAI Cloud Pricing gpu_index ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor corpusAI Cloud Pricing gpu_index ~/.cursor/mcp.json
- VS Code corpusAI Cloud Pricing gpu_index .vscode/mcp.json
- Zed corpusAI Cloud Pricing gpu_index ~/.config/zed/settings.json
- Windsurf corpusAI Cloud Pricing gpu_index ~/.codeium/windsurf/mcp_config.json
- Cline corpusAI Cloud Pricing gpu_index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI corpusAI Cloud Pricing gpu_index ~/.gemini/settings.json
- Grok corpusAI Cloud Pricing gpu_index .mcp.json (in your project root)
- ChatGPT corpusAI Cloud Pricing gpu_index Settings → Connectors → Advanced → Developer mode
- Claude.ai corpusAI Cloud Pricing gpu_index Settings → Connectors → Add custom connector
- LangChain corpusAI Cloud Pricing gpu_index pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http corpus-cloud-pricing-mcp https://cloud.trycorpus.ai/mcpOther tools on this server
- health
- catalog
- instances
- spot_events
- spot_hourly
- spot_daily
- spot_monthly
- spot_latest
- spot_snapshot
- ondemand
- ondemand_snapshot
- reserved
- reserved_snapshot
- gpu_models
- gpu_quotes
- gpu_snapshot
- status
- index_tickers
- index_fixing
- index_history
- index_board
- attestations
- capacity_headline
- capacity_stress
- capacity_history
- capacity_board
- tokens_models
- tokens_quotes
- tokens_fixing
- tokens_history
- tokens_board
- term_instance
- term
- azure_eviction
This list was read from the server itself, by connecting to it and calling tools/list on 3 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.