mcpField
U
Unsplash

Unsplash

Remote
pipeworx.ioMedia & Design0Updated 5w ago

About Unsplash

Unsplash is an MCP server for searching and retrieving photos, profiles, collections, and topics from Unsplash. It is for users working with visual material and offers search, discovery, and photo-related details through a broad set of tools.

Key features

  1. 01Search photos with filters
  2. 02Retrieve individual photos
  3. 03Browse editorial photo feed
  4. 04Explore users and collections
  5. 05Browse topics and topic photos
  6. 06View photo usage statistics

Use cases

  1. 01Find photos for a visual project
  2. 02Browse a photographer's work
  3. 03Explore photos in a collection or topic
  4. 04Check photo usage statistics

MCP support

Exposes Unsplash photo, user, collection, and topic tools to MCP clients through the Pipeworx gateway or as a standalone stdio server. The gateway endpoint also includes shared Pipeworx meta-tools.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/unsplash/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

@pipeworx/unsplash

Unsplash MCP — photo search, photos, users, collections. Free demo key 50 req/hr (production approval = 5000/hr).

Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.

Auth

  • Platform: PLATFORM_UNSPLASH_KEY. BYO: ?_apiKey=… (Unsplash access key).

Tools

  • search_photos(query, page?, per_page?, order_by?, collections?, content_filter?, color?, orientation?) — photo search
  • photo(id) — single photo
  • photo_random(query?, count?, collections?, topics?, username?, orientation?, content_filter?) — random photo(s)
  • photo_download(id) — download tracker URL (use the returned url)
  • photo_statistics(id, resolution?, quantity?) — usage stats
  • list_photos(page?, per_page?, order_by?) — editorial feed
  • user(username) — user profile
  • user_photos(username, page?, per_page?, order_by?, stats?, resolution?, quantity?, orientation?) — user's photos
  • user_likes(username, page?, per_page?, order_by?, orientation?) — user's liked photos
  • collections(page?, per_page?) — list collections
  • collection(id) — single collection
  • collection_photos(id, page?, per_page?, orientation?) — photos in collection
  • topics(ids?, page?, per_page?, order_by?) — topics
  • topic(id_or_slug) — single topic
  • topic_photos(id_or_slug, page?, per_page?, orientation?, order_by?) — photos in topic

Data source

https://api.unsplash.com

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "unsplash": {
      "url": "https://gateway.pipeworx.io/unsplash/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/unsplash/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/search_photos \
  -H 'Content-Type: application/json' \
  -d '{"query":"mountain landscape"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_photos. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "unsplash": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-unsplash"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-unsplash

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Unsplash data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.