3dassets
Related Servers
Alternatives to 3dassets
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to search and retrieve metadata and download links for CC0 HDRIs, textures, and 3D models from PolyHaven's public library.6ISC
- AlicenseNot gradedqualityDmaintenanceEnables processing, validation, optimization, and analysis of 3D models with glTF/GLB support, including format conversion, compression (Meshopt/Draco), texture optimization, and detailed model statistics.17 npmMIT
- FlicenseAqualityDmaintenanceEnables AI clients to search, browse, inspect, and download 3D models from Sketchfab via the Model Context Protocol.52-
- AlicenseNot gradedqualityBmaintenanceKeyless directory of 2,500+ public APIs and their OpenAPI specs, enabling AI agents to discover and interact with APIs.19 npmMIT

Soundza MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants and code to search a large library of free sound effects, music, and ambience by keywords and filters such as type, length, tempo, key, mood, and use case. It also exposes full metadata for individual sounds and themed packs, plus download links with ready-to-run curl commands for pulling the full-quality files.MIT- FlicenseAqualityDmaintenanceEnables AI agents to search and download 3D assets (models, materials, HDRs, brushes) from the BlenderKit library.21-
TDQS
Scored across 20 tools
Each tool has a clearly distinct purpose: account management, asset upload steps, asset and pack queries, metadata lists, and usage examples. The stepwise upload flow (get_upload_url, submit_asset_from_url, finalize_upload) is well-separated, and user-specific vs. general queries are unambiguous.
Most tools follow a verb-first pattern (get_, list_, search_, submit_, create_, verify_, finalize_), but 'my_assets' and 'my_packs' break this convention by using a noun phrase. This inconsistency is noticeable but not chaotic, as the verbs are otherwise regular.
With 20 tools, the server is slightly above the typical 3-15 range, but the breadth is justified by covering accounts, assets, packs, demos, metadata, and usage. It feels comprehensive rather than bloated, and each tool serves a distinct function.
The surface covers the full asset lifecycle: account creation/verification, both upload methods, asset retrieval/search/update, pack creation/search, demo listing, and supporting metadata (categories, tags, licenses, AI models). No obvious missing operations like delete are required given the immutable design (assets cannot be changed after upload).