unsplash-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNSPLASH_ACCESS_KEY | Yes | Your Unsplash API access 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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_photosA | Search for photos on Unsplash by keyword. Use this tool when you need to find photos for a specific topic or theme. Each result includes full attribution data that MUST be displayed when using the image (required by Unsplash API guidelines). |
| get_random_photosA | Get random photos from Unsplash, optionally filtered by keyword. Use this tool when you need variety or don't have a specific image in mind. Great for hero images, backgrounds, or when you want to avoid repetitive results. |
| track_downloadA | Track a photo download (REQUIRED by Unsplash API guidelines). You MUST call this function when a user downloads or saves a photo. This is required by Unsplash's API guidelines to properly credit photographers and track usage statistics. Call this AFTER the user confirms they want to download/use the image, not when just displaying search results. |
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 clearly distinct purpose: random photos, keyword search, and download tracking. There is no overlap or confusion.
All tools follow a consistent verb_noun pattern (get_random_photos, search_photos, track_download), making it easy to predict their function.
Three tools is appropriate for the scope: retrieving photos (random or search) and tracking downloads. Not excessive or insufficient.
The set covers the core workflow of finding and downloading photos with required attribution tracking. Minor gap: no tool for retrieving a specific photo by ID, but the random and search tools cover most use cases.