Game Asset Finder MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FREESOUND_API_KEY | No | 可选 Freesound API key | |
| GAME_ASSET_DATA_DIR | No | 本地索引目录 | data |
| GAME_ASSET_LOCAL_ROOTS | No | 本地素材根目录；Windows 用 ;，macOS/Linux 用 : 分隔 | |
| GAME_ASSET_MAX_RETRIES | No | 429/临时错误的重试次数 | 2 |
| GAME_ASSET_MAX_LOCAL_FILES | No | 本地索引默认文件上限 | 20000 |
| GAME_ASSET_DISABLED_SOURCES | No | 用逗号分隔的 provider id | |
| GAME_ASSET_CACHE_MAX_ENTRIES | No | 查询缓存最大条数 | 200 |
| GAME_ASSET_CACHE_TTL_SECONDS | No | 查询缓存秒数 | 600 |
| GAME_ASSET_MAX_RESPONSE_BYTES | No | 单次远程响应上限 | 16777216 |
| GAME_ASSET_PROVIDER_TIMEOUT_MS | No | 单一 provider 时限 | 15000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_game_assetsA | Search enabled remote and local game-asset sources concurrently. Results are normalized, license-filtered, relevance-ranked, de-duplicated, source-diversified, cached, and cursor-paginated. |
| get_game_assetA | Read the full normalized record for an asset returned by search_game_assets, including files, license guidance, alternates, and attribution text. |
| list_asset_sourcesA | List provider ids, supported asset kinds, enablement state, local index state, and active limits. |
| index_local_assetsA | Incrementally scan GAME_ASSET_LOCAL_ROOTS, hash changed files, read optional .asset.json metadata, and atomically refresh the local search index. Symbolic links are skipped. |
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 4 tools
Each tool has a distinct purpose: search, get details, list sources, and index. There is no overlap in functionality, making it easy for an agent to select the right tool.
All tool names follow a consistent verb_noun pattern in snake_case (get_game_asset, list_asset_sources, search_game_assets, index_local_assets). This predictable structure aids agent understanding.
Four tools cover the essential operations for a game asset finder: search, get detail, list sources, and index local assets. The count is well-scoped for the server's stated purpose.
The tools provide a complete workflow: index local assets, search across sources, retrieve detailed records, and list source info. No obvious gaps exist for the domain of finding and retrieving game assets.