Skip to main content
Glama

Feature Library

Server Details

Measured WebGPU and web UI parts with guides and pitfalls. Plan free; install licensed parts.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 11 tools

Disambiguation4/5

Each tool maps to a distinct facet of the library (validate, discover parts, get a part card, get a kit/recipe/playbook/shape, install, run probes), but the trio check / get_check / check_look is easy to misselect and find_parts vs get_kit both accept a job in words, so an agent may briefly hesitate. The long descriptions do resolve the overlap once read.

Naming Consistency4/5

Nearly all tools follow a predictable verb_noun or verb_resource pattern (get_part, get_kit, get_recipe, get_playbook, get_shape, get_brief, find_parts, check_look, install). The bare 'check' is the one outlier and the check*/get_check_* family could have been named more uniformly, but the scheme is clearly readable.

Tool Count5/5

Eleven tools is well within a comfortable range for a library that spans discovery, detail, kits, recipes, playbooks, page shapes, install and verification. Every tool appears to earn its place with no obviously redundant surface.

Completeness4/5

The surface covers the full build lifecycle: discover a part, read its card, wire a kit/recipe, follow playbooks, start from a shape, install modules and licence gates, and verify with evidence. Minor gaps remain, such as no explicit catalogue browse/listing or licence management tool, but agents can work around these via find_parts and check.

Available Tools

11 tools
checkCheck versions, licences and the checklistA
Read-only
Inspect

Free. The rules version (its hash) and the catalogue version, the checks to run on the build before calling it done, the runnable checks (get_check) that prove the ones a checklist can’t, and, with a licence token, the account’s licences and the parts it owns. Pass evidence (what the checks returned, area by area) and it says whether the build may be called done, and what is missing.

Inputs: evidence, decisions.

check_lookCheck a build’s touch on a lookA
Read-only
Inspect

Free. Runs the library’s own checker on how a build uses a look: each override is one of the look’s knobs, of its kind and in range; each switch is one of its options; and text contrast holds (WCAG AA) in each mode at the dials’ extremes with the overrides applied. Returns ok, the problems in sentences, the label the build may use ("In Splash", "Splash, tuned"; none for inspired) and, for a tuned build that passes, the stylesheet to load after the look’s.

Inputs: look (required), mode, dials, level, +2 more.

find_partsFind parts for a jobA
Read-only
Inspect

Free. Ranks the library’s parts for a job described in words, with why each fits and what it costs on the target platform (median ms a frame at 1920×1080 on a measured machine and tier). Strong matches for the job come first (each part says match: strong or loose), then looser ones; within each, parts that fit the platform and budget lead, then those over the budget (overBudget), then those that need WebGPU on a platform without it (blocked). For an interface job, 3D, simulation and effects parts rank lower. Each part says what it runs in (runsIn): raw WebGPU passes, a three.js scene, a 2D canvas or the DOM; a three.js part needs a three.js app, so check it against your renderer before installing. When the words name a look or ask for one, the matching looks come back too. Search by the job, not by a name.

Inputs: job (required), kit, limit, budget, +1 more.

get_briefGet the rulesA
Read-only
Inspect

Free. The agent protocol (rules.md) to follow, in order, when building with the library’s parts. Also the resource feature-store://rules.md.

Inputs: no named parameters.

get_checkGet a runnable checkA
Read-only
Inspect

Free. Scripts you run on your own build, in its page, for what a checklist can’t prove: layout-probe measures that nothing moves when the view changes state (column edges, row tops, controls that come and go) and that every focus ring shows whole. Without an id, the list with what each proves and how to run it; with an id, the script itself as text. Run them at every width you claim and pass the results to check({ evidence }).

Inputs: id.

get_kitGet a kit for a kind of buildC
Read-only
Inspect

Free. A tested set of parts for a kind of build (by kit id, or matched to the purpose in words), built on the foundations, with a tone applied when given: the parts with why, role, stack, needs and costs, the optional candidates, the glue you build yourself, what the library lacks, the tone’s settings and per-part knobs, and the looks that fit, at the level asked for (exact, tuned or inspired: what may change, what must stay); and the page shapes the purpose calls for (starting points for the page as a whole), or, when none fits, how to compose one.

Inputs: purpose (required), tone, level, platform.

get_partGet a part’s cardA
Read-only
Inspect

The free card always (summary, role, needs, costs, public API signatures, pitfall titles, pairs-with). With a licence token that owns the part: the licensed card too, with every pitfall in full, the guide, documented signatures, the module’s files and the changelog. Read every pitfall before building with it.

Inputs: id (required).

get_playbookRead a playbookA
Read-only
Inspect

Free. The library’s playbooks: how parts are placed, moved, made accessible and kept fast, with the reason for every rule and a checklist. Without an id, the list (title, summary, the parts each covers); with an id, the playbook in full as markdown. get_kit and get_recipe name the playbooks that cover their parts: read those (playbooks) before wiring the parts; the ones under playbooksIfUsed only when the build uses that part or does that work.

Inputs: id.

get_recipeGet a recipe for a buildA
Read-only
Inspect

Licensed (needs a licence token). The wiring for a scenario: the kit that fits, the steps in order (tier, install, tokens, wiring between the parts, glue, what to build yourself, tone, checks), and for each part you own its pitfalls in full and its guide. Parts you don’t own are listed with their titles, to buy or replace.

Inputs: scenario (required), tone, level, platform.

get_shapeGet a page shapeA
Read-only
Inspect

Free. The page shapes: starting points for a whole page by kind (app workspace, dashboard, product reveal, service landing, story, personal homepage, event, shop, game), each with its reader’s job, reading path, first screen, header, structure, phone, motion, what fits and what not to do. Without an id, the list; with an id, the shape in full; with "compose", the method for a page no shape fits, with a worked example. A shape is where to start, never a template: pick one or compose, and name it in your notes.

Inputs: id.

installInstall a partA
Read-only
Inspect

Licensed (needs a licence token that owns the part). Returns the part’s module/ files, each marked with the licence and this fetch, as resources to write unchanged into a folder of their own; plus NOTICE.md where there is one and the licence. Pin a version to be sure of what you get. Also takes a look id (e.g. splash, with a whole-library licence): the look’s stylesheet, its backdrop where it has one, the shared dials and the plain tokens, and the order to load them in.

Inputs: id (required), path, version.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Install premium, production-ready Three.js/WebGL 3D web components, templates and interactive scenes into Claude Code, Cursor & Codex. A hosted MCP for premium 3D web you own, from AETumi.
      6
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and edit Three.js scenes, materials, shaders, lights, animations, and performance in real time, preview changes live in the browser, capture frames, and turn approved changes into code. It supports vanilla Three.js and React Three Fiber across WebGL/WebGPU without modifying the project.
      5,671 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an AI agent to inspect live browser scene graphs, materials, shaders, lights, textures, animation, performance and memory, preview changes without touching project code, and convert the approved ones into vanilla or React Three Fiber source. It also provides website audits, smooth video frame capture, and Playwright/Puppeteer helpers.
      5,671 npm
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, render, and validate 3D scenes, 2D art, and games in HTML canvas using Three.js, WebGL, or Canvas 2D, with multi-angle screenshots, structured validation reports, and interactive playtesting.
      5
      -
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources