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