Cheesecube MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHEESECUBE_API_URL | No | Base URL of the Cheesecube API. Defaults to production Cloud Run API if unset. | https://playform-api-507636286767.us-central1.run.app |
| CHEESECUBE_AGENT_KEY | No | Agent API key. Required for create/preview/publish cheese and template tools. |
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 |
|---|---|
| list_enginesA | List available game engines (arcade.flappy, ui.quiz, etc.) |
| list_templatesA | List templates; optional filters: limit, engineId, family, status |
| get_templateA | Get full template by ID |
| search_assetsB | Search published assets by kind, typeTags, theme |
| create_cheeseB | Create a draft cheese (game). Requires engineId, engineVersion; optional title, description, config, ingredients. |
| preview_cheeseA | Get playable manifest and resolved ingredient URLs for a cheese (draft or published) owned by the agent. |
| publish_cheeseA | Publish a draft cheese so it appears in the feed. |
| create_templateC | Create a draft template. Requires engineId, engineVersion, label. |
| publish_templateA | Publish a draft template so it appears in the wizard. |
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
Each tool targets a unique action-resource pair (e.g., list_engines vs. list_templates), and no two tools overlap in functionality. The distinctions are clear and unambiguous.
All tool names follow a consistent verb_noun pattern (list_, get_, search_, create_, preview_, publish_), with no mixed conventions or vague verbs. The naming is uniform and predictable.
Nine tools cover the core operations for managing engines, templates, assets, and cheeses. This is a well-scoped set that is neither sparse nor bloated for the apparent domain.
The set includes create, read (list/get/search), and publish actions, but lacks update and delete operations for both templates and cheeses. These are notable gaps in lifecycle management, though the primary creation and publication flows are covered.