Pixabay MCP Server
The Pixabay MCP Server allows you to search for images on Pixabay via a Model Context Protocol server.
Search Images: Search using the
search_pixabay_imagestool with a required query stringFilter Results: Customize by image type (photo, illustration, vector), orientation (horizontal, vertical), and results per page (3-200)
Formatted Output: Receive structured results with image URLs and metadata
Configuration: Configure with a Pixabay API key and enable safe search
Error Handling: Built-in handling for API issues and invalid parameters
Provides tools for searching images on Pixabay, returning formatted results with image URLs and metadata, with options to filter by image type and orientation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pixabay MCP Server search for sunset photos with horizontal orientation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pixabay-mcp MCP Server
A Model Context Protocol (MCP) server for Pixabay image and video search with structured results & runtime validation.
This TypeScript MCP server exposes Pixabay search tools over stdio so AI assistants / agents can retrieve media safely and reliably.
Highlights:
Image & video search tools (Pixabay official API)
Runtime argument validation (enums, ranges, semantic checks)
Consistent error logging without leaking sensitive keys
Planned structured JSON payloads for easier downstream automation (see Roadmap)
Features
Tools
search_pixabay_images
Required:
query(string)Optional:
image_type(all|photo|illustration|vector),orientation(all|horizontal|vertical),per_page(3-200)Returns: human-readable text block (current) + (planned) structured JSON array of hits
search_pixabay_videos
Required:
queryOptional:
video_type(all|film|animation),orientation,per_page(3-200),min_duration,max_durationReturns: human-readable text block + (planned) structured JSON with duration & URLs
Configuration
Environment variables:
Name | Required | Default | Description |
| Yes | - | Your Pixabay API key (images & videos) |
| No | 10000 (planned) | Request timeout once feature lands |
| No | 0 (planned) | Number of retry attempts for transient network errors |
Notes:
Safe search is enabled by default.
Keys are never echoed back in structured errors or logs.
Related MCP server: Lorem Ipsum MCP Server
Usage Examples
Current (text only response excerpt):
Found 120 images for "cat":
- cat, pet, animal (User: Alice): https://.../medium1.jpg
- kitten, cute (User: Bob): https://.../medium2.jpgPlanned structured result (Roadmap v0.4+):
{
"content": [
{ "type": "text", "text": "Found 120 images for \"cat\":\n- ..." },
{
"type": "json",
"data": {
"query": "cat",
"totalHits": 120,
"page": 1,
"perPage": 20,
"hits": [
{ "id": 123, "tags": ["cat","animal"], "user": "Alice", "previewURL": "...", "webformatURL": "...", "largeImageURL": "..." }
]
}
}
]
}Error response (planned shape):
{
"content": [{ "type": "text", "text": "Pixabay API error: 400 ..." }],
"isError": true,
"metadata": { "status": 400, "code": "UPSTREAM_BAD_REQUEST", "hint": "Check API key or parameters" }
}Development
Install dependencies:
npm installBuild the server:
npm run buildWatch mode:
npm run watchInstallation
Option 1: Using npx (Recommended)
Add this to your Claude Desktop configuration:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"pixabay-mcp": {
"command": "npx",
"args": ["pixabay-mcp@latest"],
"env": {
"PIXABAY_API_KEY": "your_api_key_here"
}
}
}
}Option 2: Local Installation
Clone and build the project:
git clone https://github.com/zym9863/pixabay-mcp.git
cd pixabay-mcp
npm install
npm run buildAdd the server config:
{
"mcpServers": {
"pixabay-mcp": {
"command": "/path/to/pixabay-mcp/build/index.js",
"env": {
"PIXABAY_API_KEY": "your_api_key_here"
}
}
}
}API Key Setup
Get your Pixabay API key from https://pixabay.com/api/docs/ and set it in the configuration above. The same key grants access to both image and video endpoints.
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
Roadmap (Condensed)
Version | Focus | Key Items |
v0.4 | Structured & Reliability | JSON payload, timeout, structured errors |
v0.5 | UX & Pagination | page/order params, limited retry, modular refactor, tests |
v0.6 | Multi-source Exploration | Evaluate integrating Unsplash/Pexels abstraction |
See product.md for full backlog & prioritization.
Contributing
Planned contributions welcome once tests & module split land (v0.5 target). Feel free to open issues for API shape / schema suggestions.
License
MIT
Disclaimer
This project is not affiliated with Pixabay. Respect Pixabay's Terms of Service and rate limits.
Available Tools
2 toolssearch_pixabay_imagesC
Search for images on Pixabay
Inputs: query (required), image_type, orientation, per_page.
search_pixabay_videosC
Search for videos on Pixabay
Inputs: query (required), video_type, orientation, per_page, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have perfectly distinct purposes: one searches for images and the other searches for videos on Pixabay. There is no overlap or ambiguity between them, making it trivial for an agent to choose the correct tool based on the desired media type.
Both tools follow a consistent verb_noun pattern with 'search_pixabay_' as a prefix, followed by the media type ('images' or 'videos'). This naming convention is clear, predictable, and uniform across all tools in the set.
With only two tools, the server feels thin for a media search domain, as it lacks operations for retrieving details, downloading, or managing favorites. However, it is reasonable for a minimal search-focused interface, though agents might need workarounds for extended functionality.
The tool set is severely incomplete for a Pixabay integration, covering only search operations. There are significant gaps, such as no tools for getting image/video details, downloading media, or handling user accounts, which limits agent workflows and could lead to failures in broader tasks.
Maintenance
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
MCP server for Pixapi: check live credit pricing and balance, then generate images and video.
MCP server exposing the YourImageShare upload API (upload/list/delete) as tools for AI agents.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseDqualityDmaintenanceA Model Context Protocol server that enables searching for similar images by text description, integrating Inspire's backend image search capabilities with LLM interfaces like Claude Desktop.13GPL 3.0
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables image generation and retrieval from picsum.photos with customizable parameters like dimensions, filters, and output formats.1-
- FlicenseBqualityDmaintenanceA Model Context Protocol server that provides access to the Pexels API for searching and retrieving photos, videos, and collections.8120 PyPI30-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that exposes Pexels API tools for searching and retrieving free stock photos, videos, and curated collections, enabling AI agents to incorporate royalty-free media directly from chat.9529 npm3MIT