convert_texture_to_material — spriteship MCP Tool
convert_texture_to_material
(convert texture to material) is one of 72 tools on the
spriteship
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call convert_texture_to_material from your client
- Claude Code spriteship convert_texture_to_material run in your project directory
- Claude Desktop spriteship convert_texture_to_material ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor spriteship convert_texture_to_material ~/.cursor/mcp.json
- VS Code spriteship convert_texture_to_material .vscode/mcp.json
- Zed spriteship convert_texture_to_material ~/.config/zed/settings.json
- Windsurf spriteship convert_texture_to_material ~/.codeium/windsurf/mcp_config.json
- Cline spriteship convert_texture_to_material ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI spriteship convert_texture_to_material ~/.gemini/settings.json
- Grok spriteship convert_texture_to_material .mcp.json (in your project root)
- ChatGPT spriteship convert_texture_to_material Settings → Connectors → Advanced → Developer mode
- Claude.ai spriteship convert_texture_to_material Settings → Connectors → Add custom connector
- LangChain spriteship convert_texture_to_material pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http spriteship https://spriteship.com/mcp
Other tools on this server
- get_integration_status
- whoami
- get_credits
- list_projects
- get_project
- list_characters
- plan_sync
- get_character
- get_character_manifest
- list_character_poses
- list_assets
- get_asset
- get_custom_fields
- get_frames
- list_maps
- get_map
- export_map
- get_job
- get_export_command
- select_frames
- duplicate_animation
- create_animation_from_pose
- set_asset_runtime_intent
- set_asset_collision_body
- cancel_job
- approve_automatic_pose_fallback
- approve_directional_poses
- frame_animation
- rebuild_character
- mirror_animation
- rematte_animation
- phase_split
- reprocess_asset
- create_project
- create_character
- generate_character_animation
- generate_character_turn
- resume_pose
- generate_pose
- animate_asset
- revise_asset
- regen_asset_pair
- fix_asset_seams
- create_asset
- retry_job
- generate_project_intake
- generate_project_vision
- suggest_motion_hint
- get_subscription_allowances
- retry_unusable_result
- import_asset_image
- list_ui_packs
- get_ui_pack
- get_ui_pack_batch_recovery
- resume_ui_pack_batch
- recover_ui_pack_components
- get_ui_pack_batch
- list_ui_fonts
- get_project_style_guide
- save_project_style_guide
- suggest_project_style
- create_ui_pack
- save_ui_pack_style
- validate_ui_component_layout
- generate_ui_pack
- revise_ui_pack_png
- rename_ui_component
- save_ui_component_defaults
- replace_ui_component_png
- create_ui_composition
- get_ui_pack_export_command
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.