Unsplash MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_photosA | |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'search_photos' has a clearly defined and distinct purpose.
The single tool follows a clear verb_noun pattern ('search_photos'), and with only one tool, there is perfect consistency by definition.
A single tool for an Unsplash server feels thin and incomplete for the domain. While search is a core function, typical photo services would include additional operations like getting photo details, downloading, or user-related actions.
The tool surface is severely incomplete for an Unsplash server. There are significant gaps: no ability to get photo details by ID, download photos, access user profiles, collections, or statistics. The server only supports search, which limits agent workflows.