Blendkit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLENDERKIT_API_KEY | Yes | Your Blendkit API key for authentication. Recommended for higher rate limits and access to paid/private assets. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_blendkit_assetsA | Search for 3D assets in the Blendkit library. Args: query: The search term (e.g. 'chair', 'wood'). asset_type: Type of asset to search for ('model', 'material', 'scene', 'hdr', 'brush'). limit: Number of results to return (max 15). Returns: A dictionary containing a list of asset objects. Each asset contains its id, name, thumbnailUrls, and a 'files' array. Inside the 'files' array, you can find 'downloadUrl's that can be used to download the actual .blend or texture files. |
| get_asset_download_urlA | Get the download URLs for a specific asset by its ID. Args: asset_id: The ID of the asset (either 'id' or 'assetBaseId'). Returns: Dictionary containing the download URLs for the asset files. Note: The Agent should use standard tools like curl/wget with the header 'Authorization: Bearer $BLENDERKIT_API_KEY' if downloading paid/private assets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches for assets, the other retrieves download URLs for a specific asset. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern using snake_case: get_asset_download_url and search_blendkit_assets.
With only two tools, the surface feels limited for a 3D asset library. While search and download form a minimal workflow, additional tools for categories or asset details would improve scope.
The tools cover the essential search-to-download flow. Minor gaps exist, such as missing asset detail retrieval or category listing, but the core functionality is present.