LottieFiles MCP Server
# LottieFiles MCP Server
[](https://smithery.ai/server/mcp-server-lottiefiles)
A Model Context Protocol (MCP) server for searching and retrieving Lottie animations from LottieFiles.
## Features
- Search Lottie animations
- Get animation details
- Get popular animations list
## Installation
### Installing via Smithery
To install LottieFiles Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/mcp-server-lottiefiles):
```bash
npx -y smithery install mcp-server-lottiefiles --client claude
```
### Manual Installation
```bash
npm install
```
## Usage
1. Start the server:
```bash
npm start
```
2. Connect using an MCP client
## API Tools
### Search Animations
Search for Lottie animations by keywords.
Parameters:
- `query`: Search keywords
- `page`: Page number (optional, default: 1)
- `limit`: Items per page (optional, default: 20)
### Get Animation Details
Get detailed information about a specific Lottie animation.
Parameters:
- `id`: Unique identifier of the animation
### Get Popular Animations
Get a list of currently popular Lottie animations.
Parameters:
- `page`: Page number (optional, default: 1)
- `limit`: Items per page (optional, default: 20)
## Development
```bash
# Build
npm run build
```
## License
MIT
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.