Runware MCP vs Pexels
A side-by-side look at the Runware MCP and Pexels MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
PexelsMultimedia Process · Local subprocess (stdio)Pexels MCP.55GoodAuth: not declaredVerdict: choose Runware MCP for multimedia process work as a local process; choose Pexels for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Runware MCP when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
RUNWARE_API_KEY. - You want tools like
run, model_schema, list_models.
Choose Pexels when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_PEXELS_KEY. - You want tools like
photo_search, photo_curated, photo.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Pexels | |
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 55/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | RUNWARE_API_KEY | PLATFORM_PEXELS_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 12 | 8 |
| Full listing | View Runware MCP | View Pexels |
Tools & capabilities
Runware MCP tools 12
runexecute any Runware inference task (image, video, audio, 3D, upscaling, captioning, etc.) on a given modelmodel_schemafetch the parameter schema for a specific modellist_modelslist Runware's official, curated model integrations (supports `capability`, `category`, `creator`, `search` filters)model_detailsget full metadata for a curated model by AIRmodel_examplesget sample input/output pairs for a curated modelmodel_pricingget pricing overview + per-configuration examples for a curated modellist_capabilitieslist every model capability (e.g. `io:text-to-image`, `op:upscale`) with labelsmodel_searchsearch the community model catalog (Civitai fine-tunes, custom uploads)media_storagestore media (images, video, audio, 3D models) for use as input, or delete stored mediamodel_uploadupload a custom modelaccountretrieve account information including balance and usageget_task_detailsretrieve the original request and response for a previous task
Pexels tools 8
photo_searchSearch Pexels photos by keyword (required); returns paginated results with image URLs in multiple sizes, photographer name, and attribution link.photo_curatedFetch Pexels' curated editorial photo feed; returns paginated photo objects with image URLs in multiple sizes (original, large, medium, small, tiny) and photographer info.photoFetch full metadata for a single Pexels photo by numeric id, including all sized image URLs, photographer name/URL, dimensions, and alt text.video_searchSearch Pexels videos by keyword (required); returns paginated results with video file URLs at multiple resolutions, duration, and videographer info.video_popularFetch Pexels' popular video feed; returns paginated video objects with file URLs at multiple resolutions, duration, and videographer info.videoFetch full metadata for a single Pexels video by numeric id, including file URLs at all available resolutions, duration, width, height, and videographer attribution.featured_collectionsList Pexels' featured curated collections; returns collection id, title, description, and media counts for photos and videos.collection_mediaFetch all photos and videos inside a specific Pexels collection by string id; returns paginated mixed media objects with URLs and metadata.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Runware MCP
{
"mcpServers": {
"mcp-203": {
"command": "npx",
"args": [
"-y",
"@runware/mcp"
],
"env": {
"RUNWARE_API_KEY": "YOUR_RUNWARE_API_KEY_HERE"
}
}
}
}
Pexels
{
"mcpServers": {
"pexels-3": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-pexels"
],
"env": {
"PLATFORM_PEXELS_KEY": "YOUR_PLATFORM_PEXELS_KEY_HERE"
}
}
}
}
Frequently asked questions
Runware MCP is categorized under Multimedia Process and uses a local stdio subprocess. Pexels belongs to Multimedia Process and uses a local stdio subprocess. Pick Runware MCP for multimedia process work and Pexels for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Runware MCP has no declared pricing — check the project's own site. Pexels has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-203 and pexels-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Runware MCP has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Pexels has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.