Pixabay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PIXABAY_API_KEY | Yes | API key for Pixabay, obtainable from https://pixabay.com/api/docs/ |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_imagesB | |
| search_videosB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches for images and the other searches for videos. There is no overlap in functionality, and the descriptions explicitly differentiate between media types, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun pattern with 'search_' prefix followed by the media type (images/videos). The naming is perfectly uniform and predictable across the tool set.
With only two tools, this server feels thin for a media search service. While search is core, there are obvious gaps like fetching specific media by ID, getting trending content, or managing downloads. The count is too low for comprehensive coverage of the Pixabay domain.
The tool surface is severely incomplete for a Pixabay API server. It only provides search functionality, missing essential operations like retrieving specific images/videos by ID, getting user uploads, or accessing categories/trends. Agents will hit dead ends when trying to perform basic media retrieval tasks beyond searching.