MCPollinations Multimodal MCP Server
[](https://smithery.ai/server/@pinkpixel-dev/mcpollinations)
A Model Context Protocol (MCP) server that enables AI assistants to generate images, text, and audio through the Pollinations APIs
Features
- Generate image URLs from text prompts
- Generate images and return them as base64-encoded data AND save as png, jpeg, jpg, or webp (default: png)
- Generate text responses from text prompts
- Generate audio responses from text prompts
- List available image and text generation models
- No authentication required
- Simple and lightweight
- Compatible with the Model Context Protocol (MCP)
System Requirements
- **Node.js**: Version 14.0.0 or higher - For best performance, we recommend Node.js 16.0.0 or higher - Node.js versions below 16 use an AbortController polyfill
Quick Start
Installing via Smithery
To install mcpollinations for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@pinkpixel-dev/mcpollinations):
The easiest way to use the MCP server:
If you prefer to install it globally:
Or clone the repository:
MCP Integration
To integrate the server with applications that support the Model Context Protocol (MCP):
- Generate an MCP configuration file:
- Follow the prompts to customize your configuration or use the defaults. - Set custom output and temporary directories (defaults to relative paths for portability) - Configure default parameters for image generation (with a list of available models, dimensions, etc.) - Configure default parameters for text generation (with a list of available models) - Configure default parameters for audio generation (voice) - Specify which tools should be allowed
- Copy the generated `mcp.json` file to your application's MCP settings .json file.
- Restart your application.
After integration, you can use commands like:
"Generate an image of a sunset over the ocean using MCPollinations"
Troubleshooting
"AbortController is not defined" Error
If you encounter this error when running the MCP server:
This is usually caused by running on an older version of Node.js (below version 16.0.0). Try one of these solutions:
- **Update Node.js** (recommended): - Update to Node.js 16.0.0 or newer
- **Use Global Installation** - Update to the latest version of the package: ```bash npm install -g @pinkpixel/mcpollinations # Run with npx npx @pinkpixel/mcpollinations ```
- **Install AbortController manually**: - If for some reason the polyfill doesn't work: ```bash npm install node-abort-controller ```
Check Your Node.js Version
To check your current Node.js version:
If it shows a version lower than 16.0.0, consider upgrading for best compatibility.
Available Tools
The MCP server provides the following tools:
- `generateImageUrl` - Generates an image URL from a text prompt
- `generateImage` - Generates an image, returns it as base64-encoded data, and saves it to a file by default (PNG format)
- `respondAudio` - Generates an audio response to a text prompt (customizable voice parameter)
- `respondText` - Responds with text to a prompt using text models (customizable model parameter)
- `listImageModels` - Lists available models for image generation
- `listTextModels` - Lists available models for text generation
- `listAudioVoices` - Lists all available voices for audio generation
Image Generation Details
Default Behavior
When using the `generateImage` tool:
- Images are saved to disk by default as PNG files
- The default save location is the current working directory where the MCP server is running
- The 'flux' model is used by default
- A random seed is generated by default for each image (ensuring variety)
- Base64-encoded image data is always returned, regardless of whether the image is saved to a file
Customizing Image Generation
Where Images Are Saved
When using Claude or another application with the MCP server:
- **Images are saved in the current working directory of where the MCP server is running**, not where Claude or the client application is installed.
- If you start the MCP server manually from a specific directory, images will be saved there by default.
- If Claude Desktop launches the MCP server automatically, images will be saved in Claude Desktop's working directory (typically in an application data folder).
Finding Your Generated Images
- The response from Claude after generating an image includes the full file path where the image was saved
- You can specify a familiar location using the `outputPath` parameter
- Best practice: Ask Claude to save images to an easily accessible folder like your Pictures or Downloads directory
Unique Filenames
The MCP server ensures that generated images always have unique filenames and will never overwrite existing files:
- **Default filenames** include: - A sanitized version of the prompt (first 20 characters) - A timestamp - A random suffix
- **Custom filenames** are also protected: - If you specify a filename and a file with that name already exists, a numeric suffix will be added automatically - For example: `sunset.png`, `sunset_1.png`, `sunset_2.png`, etc.
This means you can safely generate multiple images with the same prompt or filename without worrying about overwriting previous images.
Accessing Base64 Data
Even when saving to a file, the base64-encoded image data is always returned and can be used for:
- Embedding in web pages (`<img src="data:image/png;base64,..." />`)
- Passing to other services or APIs
- Processing in memory without filesystem operations
- Displaying in applications that support data URIs
For Developers
If you want to use the package in your own projects: