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 |
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
| Name | Description |
|---|---|
| pexels_search_photosC | Search for photos on Pexels |
| pexels_search_videosB | Search for videos on Pexels |
| pexels_get_photoA | Get details for a specific photo by ID |
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 3 tools
Each tool has a distinct purpose: retrieving a single photo by ID, searching photos, and searching videos. There is no overlap or ambiguity.
All tools follow the 'pexels_verb_noun' pattern consistently, making the naming predictable and easy to understand.
With only 3 tools, the server is tightly scoped to core Pexels operations. This is appropriate for a focused API wrapper.
Covers search for both photos and videos and retrieval of a specific photo, but lacks a tool to get a specific video by ID, which is a notable gap given symmetrical functionality.