Server Configuration
Describes the environment variables required to run the server.
Name | Required | Description | Default |
---|---|---|---|
PORT | No | Port to use for SSE transport | 3000 |
DEBUG | No | Enable debug mode (true/false) | false |
LOG_FILE | No | Path to log file (when LOG_DESTINATION is file) | |
LOG_LEVEL | No | Log level (debug, info, warn, error) | info |
SUPABASE_URL | Yes | Supabase URL for database connection | |
MCP_TRANSPORT | No | Transport type (stdio or sse) | stdio |
OPENAI_API_KEY | Yes | OpenAI API key for AI functionality | |
LOG_DESTINATION | No | Log destination (stdout, stderr, file, none) | stderr (for stdio transport), stdout (for sse transport) |
ENABLE_ALL_TOOLS | No | Enable or disable all tools globally | true |
ENABLE_CINEMATIC_TOOLS | No | Enable or disable all cinematic tools | true |
SUPABASE_SERVICE_ROLE_KEY | Yes | Supabase service role key for authentication | |
ENABLE_VECTOR_SEARCH_TOOLS | No | Enable or disable all vector search tools | true |
ENABLE_CODE_EXAMPLE_SEARCH_TOOL | No | Enable or disable code example search tool | true |
ENABLE_GAME_RESOURCE_SEARCH_TOOL | No | Enable or disable game resource search tool | true |
Schema
Prompts
Interactive templates invoked by user choice
Name | Description |
---|---|
system-prompt-for-agent8-sdk | System prompt for Agent8 SDK |
Resources
Contextual data attached and managed by the client
Name | Description |
---|---|
No resources |
Tools
Functions exposed to the LLM to take actions
Name | Description |
---|---|
game_cinematic_generate | Generates high-quality game cinematics based on game context and reference images. This tool enables game developers to quickly create high-quality cinematics for storytelling, game trailers, cutscenes, or promotional materials. [WHEN TO USE] Use this tool when you need to:
[KEY FEATURES]
[TIPS FOR BEST RESULTS]
This tool uses the fal.ai API for image generation and video rendering. |
cinematic_result | Retrieves the result of a queued cinematic generation request. Use this tool to get the generated cinematic results. When queue processing is complete, the generated cinematic assets (image or video URLs) will be returned. |
cinematic_status | Checks the status of a queued cinematic generation request. Use this tool to monitor the progress of cinematic generation. You can obtain information about processing status, estimated completion time, and more. Note that the status typically doesn't change within 30 seconds. To avoid unnecessary API calls and optimize resource usage, it's recommended to wait at least 30 seconds between status checks. |
cinematic_cancel | Cancels a queued cinematic generation request. Use this tool to stop a long cinematic generation request or to cancel a request submitted with incorrect parameters. |
cinematic_models_list | Lists available AI models that can be used for cinematic generation. Use this tool to discover models suitable for different cinematic styles, resolutions, and quality levels. |
cinematic_model_schema | Retrieves the detailed schema for a specific cinematic generation model. This helps understand the parameters and capabilities of the model for advanced cinematic creation. |
search_code_examples | Searches and retrieves relevant game development code examples from a vector database based on specific game development requirements or programming challenges. This tool performs semantic search to find code snippets and examples that match the user's game development needs. It analyzes both the user message and associated tags to identify the most appropriate game code examples from the database. [WHEN TO USE THIS TOOL] You should use this tool whenever the user asks about game implementation details, game programming patterns, specific game feature implementations, or requests examples of how to implement something in game development. USE THIS TOOL if the user mentions specific game programming tasks, asks "how do I code X in my game", or needs reference implementations for game mechanics, rendering, physics, AI, or other game-specific systems. The results are returned in a structured format containing game client code, game server code, and descriptive explanations when available. The userMessage parameter should include detailed context about the game programming challenge or implementation requirement, while the tags parameter should specify relevant game engines, frameworks, or concepts to narrow the search scope. Note: This tool does not generate complete games but rather provides existing code snippets and examples that address specific game implementation challenges. The quality of search results heavily depends on the clarity and specificity of the provided user message and tags. Examples typically demonstrate solutions to common game implementation problems and can be used as reference material for your own game development work. Common scenarios where this tool is useful include: 1) When a user asks "How do I implement character movement in Unity?", 2) When they need examples of game state management for specific operations, 3) When they want to see how others have implemented a specific game UI component, 4) When they need patterns for game networking, 5) When they request code for handling specific game physics edge cases. IMPORTANT: You should proactively offer to search for game code examples whenever a user is discussing game implementation details or asking how to build something in a game, even if they don't explicitly request examples. Always prefer showing existing, tested game code examples over generating new code when possible. If you are uncertain whether relevant game code examples exist for a user's question, it is better to use this tool and check rather than assume none are available. Even partial matches can provide valuable game implementation insights to users. |
search_game_resources | Searches and retrieves relevant game development assets from a vector database based on natural language descriptions. This tool performs semantic search to find game assets such as 3D models, textures, sounds, and animations that match the user's requirements. [WHEN TO USE THIS TOOL] Use this tool when users need to find specific game assets by describing what they're looking for, such as: 1) "A medieval knight character sprite sheet", 2) "Running animation for a humanoid character", 3) "Weapon swing sound effect", 4) "Forest environment background". The tool uses semantic similarity to find the most relevant assets based on their descriptions. Results include asset descriptions, URLs, and any associated metadata. |