game-dev-resource-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub personal access token to improve API rate limits. Never commit tokens. |
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 |
|---|---|
| find_game_assetsA | Search all supported asset providers at once, apply commercial/license filters, and return ranked results with explainable match reasons. This is the preferred tool when the user describes the asset they need without naming a source site. |
| search_game_assetsC | Search the local registry of game-development resource sources. |
| search_live_assetsA | Search one supported asset provider. Providers may be live APIs or maintained verified catalogs; results preserve source and license provenance. |
| get_asset_filesA | Return official provider-hosted download links and file metadata for a selected asset without mirroring it. |
| list_asset_providersA | List supported asset providers and whether each is a live API or verified catalog. |
| search_open_source_projectsB | Search GitHub repositories for reusable game-development code. Inspect the explicit repository license before reuse. |
| check_licenseB | Classify a known license using conservative game-commercial-use rules. |
| inspect_repositoryA | Inspect a GitHub repository's public metadata and detected license. Accepts owner/name. |
| generate_attributionB | Generate a conservative attribution/CREDITS entry for a resource after its license has been identified. |
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 9 tools
Most tools have clearly distinct purposes, but there is some overlap between search_game_assets and find_game_assets, and between check_license and inspect_repository. Descriptions help resolve these, but the boundaries could be sharper.
All tool names follow a consistent verb_noun pattern (e.g., search_open_source_projects, check_license, get_asset_files). No mixed conventions or vague verbs.
9 tools is well-scoped for a game development resource server. Each tool covers a distinct step in the workflow without redundancy or bloat.
The tool set covers the full lifecycle: searching for code and assets, inspecting licenses, retrieving file links, listing providers, and generating attribution. No significant gaps for the stated purpose.