aetumi-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 |
|---|---|
| list_threejs_recipesA | List expert, production-grade Three.js / WebGL recipes (glTF Draco/Meshopt loading, KTX2 texture compression, instancing & LOD, scroll-scrub, postprocessing bloom, raycasting). Returns ids, titles and keywords. |
| get_threejs_recipeA | Get one full Three.js / WebGL recipe by id — includes when-to-use, ready-to-paste code (Three.js r160+, ESM) and expert notes. Ids: scene-scaffold, gltf-draco-meshopt, ktx2-textures, instancing-lod, scroll-scrub, postprocessing-bloom, raycast-interaction. |
| audit_3d_web_performanceA | Return the AETumi 3D-web performance checklist — the highest-leverage rules for shipping fast, interactive Three.js / WebGL websites (DPR cap, Draco/Meshopt, KTX2, instancing, lazy-init, disposal, reduced-motion). |
| list_templatesA | List AETumi's premium interactive 3D website templates (Three.js / WebGL, React / Next.js) — you own the full source of each. |
| get_templateA | Get details for one AETumi 3D website template by id (aerae, aerae-luxe, aesport, aebiker, avelor). |
| connect_infoA | How to connect the full hosted AETumi MCP (streamable-HTTP) to Claude Code, Cursor or Codex for premium 3D web components, templates & scenes. |
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 6 tools
Each tool targets a clearly distinct resource or action: recipe listing/retrieval, template listing/retrieval, performance audit, and connection info. The list/get pairs are conventional and the recipe-vs-template distinction is reinforced by descriptions.
Most tools follow a clear verb_noun pattern (list_*, get_*) with plural list and singular get forms. Minor inconsistencies include audit_3d_web_performance mixing '3d' with the otherwise 'threejs' terminology, and connect_info being a noun-ish name rather than a strict verb_noun.
Six tools is a well-scoped set for a specialized 3D recipe/template/performance resource. Each tool has a clear purpose and none feel redundant or missing at the surface level.
The server provides list/get coverage for both recipes and templates, plus an audit checklist and connection guidance, which covers the main discovery workflow. It lacks direct template source retrieval or search/filter capabilities, but those are not clearly required for this read-oriented MCP.