PicoBerry MCP Server
Related Servers
Alternatives to PicoBerry MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables generating 3D models from text prompts, rendering turntable animations, and uploading them directly to YouTube via an MCP interface.1415MIT

Context3D MCP Serverofficial
AlicenseBqualityDmaintenanceEnables AI-powered 3D model generation from text and images with PBR textures, supporting blockchain authentication and MCP integration.6711 npmMIT- AlicenseAqualityBmaintenanceMCP server for Pixmax API enabling generation of images, video, text, audio, and 3D across dozens of models like Midjourney, Kling, and ElevenLabs.10MIT
- AlicenseAqualityDmaintenanceAn MCP server implementation that integrates with 4o-image API, enabling LLMs and other AI systems to generate and edit images through a standardized protocol. Create high-quality art, 3D characters, and custom images using simple text prompts.158 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered image and video generation using Higgsfield AI models through MCP-compatible clients like Claude Desktop and Perplexity.383 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Blockbench, a 3D modeling tool for Minecraft, through a plugin-based MCP server.GPL 3.0
TDQS
Scored across 14 tools
The tools mostly have distinct purposes, and descriptions clearly separate generation, post-processing, and retrieval. However, get_asset, wait_for_asset, and download_asset all return asset-related outcomes and could initially be confused, and generate_image vs generate_3d_from_image require careful reading to pick the right one.
Most tools follow a clear verb_noun pattern (list_*, get_*, generate_*, download_*), but there are small deviations: generate_image lacks the "from_text" detail that generate_3d_from_image/text have, and parts_board is a noun phrase rather than a verb-based name. The overall style is readable and only mildly inconsistent.
Fourteen tools cover generation, post-processing (remesh, texture, animate, parts_board), and asset management (list, get, wait, download, credits). This is a well-scoped number, and each tool has a clear role with no obvious bloat or excessive overlap.
The server covers core workflows: 2D and 3D generation, common post-processing transforms, result retrieval, and export. The main missing piece is an imported-3D-asset upload path (you can only modify assets created within the system) and asset deletion, but these are relatively minor gaps and do not cause dead ends in normal use.