GSAP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The Node environment (e.g., development, production). Used in Claude Desktop config as an env variable. | production |
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 | {} |
Tools
Functions exposed to the LLM to take actions
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 43 tools
While many tools have distinct purposes, the large number leads to overlap. For example, multiple timeline-related tools (create_sync_timeline, sync_timeline_playback, timeline_scrubber) could be confused, and generic tools like sequence_animation and parallel_animation overlap with timeline and batch tools.
Tool names generally follow a verb_noun pattern, but there are inconsistencies: some use 'generate' vs 'create', and several lack a verb (e.g., svg_morph_animation, timeline_scrubber). The mix of English and Chinese descriptions also adds inconsistency.
With 43 tools, the server is excessively large for a typical MCP server. While GSAP is a complex library, this many tools could be reduced by combining related functionalities into fewer, more composable tools.
The tool set covers virtually all major GSAP features: basic animations, timelines, scroll, SVG, text, physics, 3D, responsive, debugging, performance, and plugin management. It is very comprehensive for the GSAP domain.