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