LottieFiles MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_animationsC | Search for Lottie animations by keywords, tags, and other criteria. Supports pagination. |
| get_animation_detailsB | Get detailed information about a specific Lottie animation, including animation data, preview images, and tags. |
| get_popular_animationsB | Get a list of currently popular Lottie animations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_animations | Search for Lottie animations |
| get_popular_animations | Get popular Lottie animations |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| popular | Popular Lottie animations |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_animation_details retrieves metadata for a specific animation, get_popular_animations lists trending animations, and search_animations enables keyword-based discovery. There is no overlap in functionality, making tool selection straightforward.
All tool names follow a consistent verb_noun pattern with snake_case (get_animation_details, get_popular_animations, search_animations). The naming is predictable and enhances readability across the set.
With only 3 tools, the server feels thin for a Lottie animation platform. While the tools cover basic retrieval and search, the absence of creation, update, or management operations suggests limited scope, though it may be intentional for a read-only interface.
The toolset is severely incomplete for a typical animation platform, lacking any CRUD operations (e.g., upload_animation, update_animation, delete_animation) or interaction features (e.g., like_animation, download_animation). Agents can only retrieve and search, which may lead to dead ends in workflows requiring modification.