Freepik MCP Server

Created By
Toos00a year ago
A Model Context Protocol (MCP) server to interact with the Freepik.com API.- Un serveur MCP (Model Context Protocol) pour interagir avec l'API de Freepik.com.
Overview

what is Freepik MCP Server?

Freepik MCP Server is a Model Context Protocol (MCP) server designed to interact with the Freepik.com API, allowing users to search for images and vector graphics, and retrieve image details.

how to use Freepik MCP Server?

To use the Freepik MCP Server, clone the repository, install the dependencies, set your Freepik API key as an environment variable, and start the server using Python.

key features of Freepik MCP Server?

  • Advanced image search with filters
  • Vector graphics search
  • Retrieve specific image details
  • Error handling and logging
  • Automated testing with CI/CD integration

use cases of Freepik MCP Server?

  1. Searching for images based on specific queries and filters.
  2. Retrieving detailed information about images from Freepik.
  3. Integrating image search capabilities into applications using the Freepik API.

FAQ from Freepik MCP Server?

  • What are the prerequisites for using Freepik MCP Server?

You need Python 3.10 or higher and a Freepik API key.

  • How do I obtain a Freepik API key?

You can obtain an API key by signing up at Freepik.com and following their API documentation.

  • Are there any limitations when using the Freepik API?

Yes, request limits depend on your subscription plan, and some features may require a premium account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Toos00
Star
0
Language
Python
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