get_workload_cost — Compute Screener MCP Tool Read-only
get_workload_cost
(get workload cost) is one of 14 tools on the
Compute Screener
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_workload_cost from your client
- Claude Code Compute Screener get_workload_cost run in your project directory
- Claude Desktop Compute Screener get_workload_cost ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Compute Screener get_workload_cost ~/.cursor/mcp.json
- VS Code Compute Screener get_workload_cost .vscode/mcp.json
- Zed Compute Screener get_workload_cost ~/.config/zed/settings.json
- Windsurf Compute Screener get_workload_cost ~/.codeium/windsurf/mcp_config.json
- Cline Compute Screener get_workload_cost ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Compute Screener get_workload_cost ~/.gemini/settings.json
- Grok Compute Screener get_workload_cost .mcp.json (in your project root)
- ChatGPT Compute Screener get_workload_cost Settings → Connectors → Advanced → Developer mode
- Claude.ai Compute Screener get_workload_cost Settings → Connectors → Add custom connector
- LangChain Compute Screener get_workload_cost pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http compute-screener https://computescreener.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.