MCP Scroll Animation Analyzer
Server 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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_pageA | Open a webpage in headless browser for analysis. This initializes the browser and navigates to the URL. |
| scroll_and_recordB | Scroll through the entire page while recording video and capturing scroll-triggered animations. |
| extract_animation_codeB | Extract GSAP, ScrollTrigger, and Lenis code using AST parsing. Much more reliable than regex. |
| interact_with_pageB | Perform interactions on the page (click, hover, scroll to element, type). |
| get_element_animationsB | Get detailed animation information for a specific element. |
| capture_current_stateB | Capture a screenshot and animation state at the current scroll position. |
| get_scroll_triggersA | Get all ScrollTrigger instances on the page with their configurations. |
| analyze_lenisA | Analyze Lenis smooth scroll configuration and behavior. |
| generate_reportC | Generate a comprehensive report of the scroll animation analysis. |
| close_browserA | Close the browser and clean up resources. |
| set_output_directoryB | Set the directory where analysis output will be saved. |
| deep_script_analysisC | Perform deep analysis of all JavaScript for animation patterns. |
| watch_elementC | Watch a specific element for style/transform changes during scroll. |
| get_animation_cssA | Extract all CSS animations and keyframes from the page stylesheets. |
| trace_animation_executionC | Inject tracing to capture GSAP calls in real-time during scroll. |
| export_replicable_codeC | Generate standalone code to recreate the observed animations. |
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 16 tools
Each tool targets a distinct aspect of scroll animation analysis, from opening and interacting with the page to extracting code, monitoring elements, and exporting replicas. Some tools like extract_animation_code and deep_script_analysis have overlapping domains, but their descriptions clarify different purposes.
Most tools follow a verb_noun pattern (open_page, get_scroll_triggers, generate_report), but a few deviations like scroll_and_record (two verbs) and deep_script_analysis (noun phrase) break the convention. This is mostly consistent with minor exceptions.
With 16 tools, the server is slightly above the typical well-scoped range but each tool serves a clear purpose in the analysis workflow. No tools are redundant, though some could potentially be consolidated.
The toolset covers the full analysis lifecycle: page opening, interaction, scrolling, recording, extracting CSS/JS code, monitoring elements, tracing execution, generating reports, and exporting code. There are no obvious gaps or dead ends.