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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago