check_local_viability — Local Model Suitability MCP MCP Tool Read-only
check_local_viability
(check local viability) is one of 1 tool on the
Local Model Suitability MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_local_viability from your client
- Claude Code Local Model Suitability MCP check_local_viability run in your project directory
- Claude Desktop Local Model Suitability MCP check_local_viability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Local Model Suitability MCP check_local_viability ~/.cursor/mcp.json
- VS Code Local Model Suitability MCP check_local_viability .vscode/mcp.json
- Zed Local Model Suitability MCP check_local_viability ~/.config/zed/settings.json
- Windsurf Local Model Suitability MCP check_local_viability ~/.codeium/windsurf/mcp_config.json
- Cline Local Model Suitability MCP check_local_viability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Local Model Suitability MCP check_local_viability ~/.gemini/settings.json
- Grok Local Model Suitability MCP check_local_viability .mcp.json (in your project root)
- ChatGPT Local Model Suitability MCP check_local_viability Settings → Connectors → Advanced → Developer mode
- Claude.ai Local Model Suitability MCP check_local_viability Settings → Connectors → Add custom connector
- LangChain Local Model Suitability MCP check_local_viability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http local-model-suitability-mcp https://local-model-suitability-mcp-production.up.railway.app
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.