MCP Game Development Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_game_projectC | Create a new game project with Linear integration and setup |
| update_game_knowledgeC | Update knowledge about game development best practices and technologies |
| get_game_templatesB | Get available game templates |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: create_game_project handles project initialization, get_game_templates provides template retrieval, and update_game_knowledge manages knowledge updates. The descriptions clearly differentiate between project creation, template access, and knowledge management functions.
All tools follow a consistent verb_noun naming pattern (create_game_project, get_game_templates, update_game_knowledge) with clear, descriptive names. The naming convention is uniform throughout the set, making it easy to understand each tool's function at a glance.
With only 3 tools, the set feels thin for a game development server that presumably needs to handle various development tasks. While the tools cover project creation, templates, and knowledge, there are likely missing operations for actual game development workflows like asset management, testing, or deployment.
The tool surface is significantly incomplete for game development. While it covers project setup and knowledge management, it lacks essential CRUD operations for game assets, code editing, testing, debugging, or deployment. There are no tools for managing game objects, scenes, or actual development tasks beyond initial setup.