get_shader_portability_report — GameDev.net MCP Tool Read-only
get_shader_portability_report
(get shader portability report) is one of 10 tools on the
GameDev.net
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_shader_portability_report from your client
- Claude Code GameDev.net get_shader_portability_report run in your project directory
- Claude Desktop GameDev.net get_shader_portability_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GameDev.net get_shader_portability_report ~/.cursor/mcp.json
- VS Code GameDev.net get_shader_portability_report .vscode/mcp.json
- Zed GameDev.net get_shader_portability_report ~/.config/zed/settings.json
- Windsurf GameDev.net get_shader_portability_report ~/.codeium/windsurf/mcp_config.json
- Cline GameDev.net get_shader_portability_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GameDev.net get_shader_portability_report ~/.gemini/settings.json
- Grok GameDev.net get_shader_portability_report .mcp.json (in your project root)
- ChatGPT GameDev.net get_shader_portability_report Settings → Connectors → Advanced → Developer mode
- Claude.ai GameDev.net get_shader_portability_report Settings → Connectors → Add custom connector
- LangChain GameDev.net get_shader_portability_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://gamedev.net/mcp/Other 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.