Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for searching Pexels stock photos, videos, and curated collections.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
PEXELS_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pexels": {
"command": "npx",
"args": [
"-y",
"mcp-pexels"
],
"env": {
"PEXELS_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pexels --env PEXELS_API_KEY=your-value -- npx -y mcp-pexelsFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pexels": {
"command": "npx",
"args": [
"-y",
"mcp-pexels"
],
"env": {
"PEXELS_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"pexels": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-pexels"
],
"env": {
"PEXELS_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account developer-ishan, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: PEXELS_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.2) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A [Model Context Protocol](https://modelcontextprotocol.io) server that exposes the [Pexels API](https://www.pexels.com/api/) — free stock photos, videos, and curated collections — as MCP tools that any compatible AI client (Claude Desktop, Claude Code, Cursor, Cline, Continue, etc.) can call directly from a chat.
📦 npm: mcp-pexels · 🏷 Latest release: v1.0.0 · 💻 Source: developer-ishan/mcp-pexels
Photos & videos provided by Pexels.
{
"mcpServers": { "pexels": { "command": "npx", "args": ["-y", "mcp-pexels"], "env": { "PEXELS_API_KEY": "your_key_here" } } } }
Paste into your MCP client's config, restart, and the nine pexels_* tools are live. Get a free key at https://www.pexels.com/api/.
Once mcp-pexels is connected to an AI client, the agent can pull royalty-free photos and videos straight into its workflow. A few concrete uses:
pexels_popular_videos with size and duration filters.color: "orange".lorem-pixel boxes.Because every response includes a _rateLimit object, the agent can self-throttle and respect the Pexels free-tier quota (200 req/hour, 20 000/month).
| Domain | Tool | What it does |
|---|---|---|
| Photos | pexels_search_photos | Search photos by query with orientation / size / color / locale filters. |
| Photos | pexels_curated_photos | Fetch the Pexels team's real-time curated photo feed. |
| Photos | pexels_get_photo | Retrieve a single photo by its numeric id. |
| Videos | pexels_search_videos | Search videos by query with orientation / size / locale filters. |
| Videos | pexels_popular_videos | Fetch popular videos with optional width / height / duration constraints. |
| Videos | pexels_get_video | Retrieve a single video by its numeric id. |
| Collections | pexels_featured_collections | List Pexels featured collections. |
| Collections | pexels_my_collections | List the authenticated user's own collections. |
| Collections | pexels_collection_media | Retrieve the photos and videos inside a specific collection. |
Each tool response is the raw Pexels JSON merged with a top-level _rateLimit field exposing limit, remaining, and reset (UNIX timestamp).
See docs/tools/ for per-tool parameter tables and example payloads.
All paths below use npx -y mcp-pexels — no global install required. Replace your_key_here with a real Pexels API key.
Option 1 — one-click `.mcpb` install (recommended). Download the latest mcp-pexels-*.mcpb from the Releases page, double-click the file, paste your Pexels API key when Claude Desktop prompts, and click Install.
Option 2 — manual JSON config. Edit claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json{
"mcpServers": { "pexels": { "command": "npx", "args": ["-y", "mcp-pexels"], "env": { "PEXELS_API_KEY": "your_key_here" } } } }
Restart Claude Desktop.
claude mcp add pexels -e PEXELS_API_KEY=your_key_here -- npx -y mcp-pexels
Or edit ~/.claude.json directly and add the same mcpServers block as above.
Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": { "pexels": { "command": "npx", "args": ["-y", "mcp-pexels"], "env": { "PEXELS_API_KEY": "your_key_here" } } } }
Open the Cline extension settings → MCP Servers → Edit Settings. Add:
{
"mcpServers": { "pexels": { "command": "npx", "args": ["-y", "mcp-pexels"], "env": { "PEXELS_API_KEY": "your_key_here" } } } }
In ~/.continue/config.json:
{
"experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": ["-y", "mcp-pexels"], "env": { "PEXELS_API_KEY": "your_key_here" } } } ] } }
If your client supports stdio MCP servers it just needs command, args, and env. Use the same shape as Cursor / Claude Desktop above. For inspector / debugging:
export PEXELS_API_KEY=your_key_here
npx -y @modelcontextprotocol/inspector npx -y mcp-pexels
This opens a browser UI where you can call each tool interactively.
Once connected, try prompts like:
The agent will pick the appropriate tool, send the right parameters, and include photographer/videographer credit as part of its answer.
| mcp-pexels | Raw Pexels REST API | Image-only general MCP servers | |
|---|---|---|---|
| Photos | ✅ | ✅ | varies |
| Videos | ✅ | ✅ | usually ❌ |
| Collections | ✅ | ✅ | ❌ |
| Rate-limit headers exposed to agent | ✅ | ❌ (raw headers, agent must parse) | ❌ |
| Zod-validated input | ✅ | ❌ | varies |
npx-installable, zero config | ✅ | ❌ | varies |
| Type-safe TS source | ✅ | n/a | varies |
| MIT-licensed | ✅ | n/a | varies |
If you only need photos and you already have a generic image MCP server wired up, that may be enough. If you want first-class video and collection support with rate-limit awareness, this is purpose-built for it.
Sign up at https://www.pexels.com/api/ — keys are issued instantly and the free tier allows 200 requests/hour and 20 000 requests/month.
No. The Pexels API is free, the npm package is free (MIT), and mcp-pexels itself does not call any paid service.
No — the server is a thin wrapper over the Pexels HTTPS API and requires network access.
Yes, per the Pexels license, but you must attribute the platform and (when possible) the photographer. See Attribution.
Claude.ai's web product doesn't yet support stdio MCP servers — only Claude Desktop, Claude Code, and the API do. Anthropic is rolling out browser MCP support, so this should change.
No. Run it locally via npx. Because Pexels API keys are per-user, hosting a shared instance doesn't make sense.
npx always fetches the latest published version. If you've installed globally, run npm update -g mcp-pexels.
The Pexels API surface is fully implemented (9/9 endpoints as of Pexels API v1). New endpoints will be added via PR — see Contributing.
@modelcontextprotocol/inspector?Yes:
export PEXELS_API_KEY=your_key_here
npx -y @modelcontextprotocol/inspector npx -y mcp-pexels
Every tool response includes a _rateLimit object with limit, remaining, and reset (UNIX timestamp). The agent can read this and self-throttle. If Pexels returns 429, the server surfaces it as a PexelsApiError so the agent sees the failure.
It is read from the PEXELS_API_KEY env var on the local process. It never leaves your machine except in Authorization headers to api.pexels.com. Nothing is logged.
fetch and --env-file)git clone https://github.com/developer-ishan/mcp-pexels.git
cd mcp-pexels npm install echo "PEXELS_API_KEY=your_key_here" > .env
npm test # 42 mocked vitest cases, no network npm run build # tsc → dist/ npm run dev # tsx watch npm run test:watch # vitest in watch mode npm start # node --env-file=.env dist/index.js
src/
├── index.ts # MCP server entrypoint (stdio) ├── http/ │ ├── client.ts # PexelsClient (injectable fetch for tests) │ └── types.ts # PexelsApiError, RateLimit, PexelsResponse ├── tools/ │ ├── index.ts # composes the three domain factories │ ├── photos.ts # 3 photo tools │ ├── videos.ts # 3 video tools │ └── collections.ts # 3 collection tools └── types/ ├── tool.ts # defineTool helper + ToolDefinition ├── photos.ts ├──
Only the beginning is shown; read the rest in the repo