MCPollinations Multimodal MCP Server

Created By
pinkpixel-deva year ago
A Model Context Protocol (MCP) server that enables AI assistants to generate images, text, and audio through the Pollinations APIs. Supports customizable parameters, image saving, and multiple model options.
Overview

what is MCPollinations?

MCPollinations is a Model Context Protocol (MCP) server that enables AI assistants to generate images, text, and audio through the Pollinations APIs.

how to use MCPollinations?

To use MCPollinations, you can run it directly with npx, install it globally, or clone the repository from GitHub. After setting it up, you can generate images, text, and audio by sending appropriate prompts.

key features of MCPollinations?

  • Generate image URLs from text prompts
  • Generate images and return them as base64-encoded data AND save as png, jpeg, jpg, or webp
  • Generate text and audio responses from text prompts
  • List available image and text generation models
  • No authentication required
  • Simple and lightweight

use cases of MCPollinations?

  1. Creating images based on user-defined prompts
  2. Generating audio responses for interactive applications
  3. Providing text responses for chatbots and virtual assistants

FAQ from MCPollinations?

  • Is authentication required to use MCPollinations?

No, MCPollinations does not require authentication.

  • What are the system requirements?

You need Node.js version 14.0.0 or higher, preferably 16.0.0 or higher for best performance.

  • Can I customize the output format of generated images?

Yes, you can specify the format (png, jpeg, jpg, or webp) when generating images.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pinkpixel-dev
Star
17
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago