Unsplash MCP Servers Compared

There are at least five MCP servers that give AI coding agents access to stock photos. All of them connect to Unsplash or Pexels. But setup requirements vary dramatically.

Here's a side-by-side comparison of the ones that actually work.

Comparison table

The API key problem

Every Unsplash MCP server except tteg requires you to:

1. Go to unsplash.com/developers
2. Create a developer account
3. Register a new application
4. Accept their API terms
5. Copy the access key
6. Add it to your MCP server config as an environment variable

For Pexels and Pixabay, repeat the process. stock-images-mcp wants up to three API keys before it runs.

tteg handles credentials on the backend. You never touch a key.

Setup: tteg vs the rest

tteg — add to your MCP config and go:

{
  "mcpServers": {
    "tteg": {
      "command": "uvx",
      "args": ["tteg-mcp"]
    }
  }
}

That's it. No environment variables. No registration. Claude Code or Cursor can immediately search and save photos.

Any other Unsplash MCP server — typical config:

{
  "mcpServers": {
    "unsplash": {
      "command": "npx",
      "args": ["-y", "unsplash-mcp-server"],
      "env": {
        "UNSPLASH_ACCESS_KEY": "your_key_here"
      }
    }
  }
}

Where do you get your_key_here? Six steps above.

Batch mode

tteg is the only one with a batch command. Create a JSON manifest of all the images your page needs:

tteg batch manifest.json

One command fills a hero, team photo, testimonials, and about section. The others handle images one at a time.

Which one should you use?

If you want zero setup: tteg. If you already have Unsplash API credentials and want multi-source support: stock-images-mcp. If you need advanced image analysis: unsplash-smart-mcp.

For most people building websites with AI tools, the answer is: you don't want to register for anything. You want photos.

uv tool install tteg