Pexels MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEXELS_API_KEY | Yes | Your Pexels API key (get one at https://www.pexels.com/api/) |
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 | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchPhotosD | – |
| downloadPhotoD | – |
| downloadVideoD | – |
| getCuratedPhotosD | – |
| getPhotoD | – |
| searchVideosD | – |
| getPopularVideosD | – |
| getVideoD | – |
| getFeaturedCollectionsD | – |
| getCollectionMediaD | – |
| setApiKeyD | – |
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 11 tools
Tool names are distinct by resource (photo, video, collection) and action (get, search, download), but without descriptions, subtle overlaps like 'downloadPhoto' vs 'getPhoto' could confuse an agent.
All tools use consistent camelCase with a verb_noun pattern (e.g., downloadPhoto, searchVideos, setApiKey), no mixing of conventions.
11 tools cover the essential operations of the Pexels API (search, individual retrieval, curated/popular, collections, download, API key configuration) without being excessive.
The tool set covers major read operations and collections, but may lack some features like listing all collections or more detailed filtering, and no descriptions hinder full assessment.