GM-Maker MCP 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_projectA | Create a new GameMaker YYP project at the specified directory if it does not exist |
| add_scriptB | Create a new GML script and register it in the YYP |
| add_objectA | Create a GameMaker object .yy file with optional event stubs and register it in the project |
| add_sprite_from_imagesA | Import frames from a directory into a new sprite and register it in the project |
| list_resourcesA | List resource names by type from the YYP file |
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 5 tools
Each tool targets a distinct action and resource type: creating a project, listing resources, and adding sprites, scripts, or objects. There is no overlap between tools, and the purpose of each is immediately clear from its name and description.
All tool names follow a consistent verb_noun pattern (create, list, add), with lowercase snake_case throughout. The only deviation, 'add_sprite_from_images', still clearly uses the 'add_' verb and noun, maintaining a predictable structure.
With exactly 5 tools, the server is well-scoped for its purpose of creating and managing a GameMaker project. Each tool covers a core operation without unnecessary redundancy or bloat.
The server covers the primary lifecycle of creating a project and adding core resources (sprites, scripts, objects), along with listing everything. It lacks support for other GameMaker resource types (e.g., sounds, rooms) and does not offer update or delete operations, but these are minor gaps for a tool set focused on initial creation and discovery.