antics-mcp
OfficialServer 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_gameA | Deploy a single HTML game file and get a playable multiplayer URL (keyless if no projectId). |
| create_projectB | Create a project; returns its id, publishable key (pk_), and secret key (sk_, shown once). |
| get_leaderboardB | Read a project's leaderboard (top scores). |
| list_projectsB | List your projects (requires login). |
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 4 tools
Each tool targets a distinct action: project creation, game deployment, leaderboard retrieval, and project listing. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_project, deploy_game), making them predictable and easy to understand.
With only 4 tools, the server is well-scoped for its apparent purpose: project creation, game deployment, and leaderboard access. Each tool serves a clear function without bloat.
The tool surface covers core operations (create, deploy, list, read scores) but lacks update and delete tools for projects, and there is no tool for managing users or game configurations.