Which integrations are available for this server?

Provides tools for searching and browsing the Fiverr marketplace, including gig search with filters (price, seller level, category), retrieval of detailed gig information with pricing packages and descriptions, viewing seller profiles with certifications and languages, reading gig reviews, and listing available categories. Enables discovery and comparison of freelance services without requiring an API key.

fiverr-mcp-server

by KyuRish

Overview Schema Related Servers Score Discussions

Python

Remote

Fiverr MCP Server

PyPI version License: MIT

mcp-name: io.github.KyuRish/fiverr-mcp-server

MCP server for searching and browsing Fiverr - gigs, sellers, pricing, and reviews. No API key required.

Features

Search gigs by keyword with filters (price, seller level, category, sorting)
Get gig details including pricing packages (Basic/Standard/Premium), description, and tags
View seller profiles with certifications, languages, hourly rate, and gig listings
Read gig reviews from the first page of any gig
List categories to discover valid category slugs for filtered search
All prices returned in USD (not cents)
Built-in rate limiting and retry with browser fingerprint rotation
Structured error messages on failures (no raw crashes)

Related MCP server: mcp-dashboards

Installation

Using uvx (recommended)

{
  "mcpServers": {
    "fiverr": {
      "command": "uvx",
      "args": ["fiverr-mcp-server"]
    }
  }
}

Using pip

pip install fiverr-mcp-server

From source

git clone https://github.com/KyuRish/fiverr-mcp-server.git
cd fiverr-mcp-server
uv sync
uv run fiverr-mcp-server

Configuration

Add to your Claude Desktop config (claude_desktop_config.json):

Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "fiverr": {
      "command": "uvx",
      "args": ["fiverr-mcp-server"]
    }
  }
}

Environment Variables

Variable	Description	Default
`TRANSPORT`	Transport mode (`stdio` or `sse`)	`stdio`
`PROXY_URL`	Optional HTTP proxy for requests	-
`RATE_LIMIT_DELAY`	Minimum seconds between requests	`2`

Available Tools

`search_gigs`

Search the Fiverr marketplace by keyword. Returns up to 48 gigs per page with pagination info.

Parameters:

query (required) - Search query (e.g. "logo design", "python developer")
category - Category slug (use list_categories to see valid values)
min_price / max_price - Price range filter in USD
seller_level - "level_one_seller", "level_two_seller", or "top_rated_seller"
sort_by - "relevance", "best_selling", "newest", "price_asc", or "price_desc"
page - Page number for pagination

Returns: List of gigs with title, price (USD), rating, reviews count, seller name, and URL. Also includes total_results and has_more for pagination.

`get_gig_details`

Get full details of a specific gig including all pricing tiers.

Parameters:

url (required) - Fiverr gig URL or path

Returns: Title, description, seller info, packages (name/price/delivery/revisions/features), tags, metadata, rating, reviews count, category, and orders in queue.

`get_seller_profile`

Get a seller's profile. Use seller_name from search results as the username.

Parameters:

username (required) - Seller's Fiverr username

Returns: Display name, bio, location, member since, languages, certifications, hourly rate (USD), gig listings, and verification status.

`get_gig_reviews`

Get the first page of reviews for a gig (typically 5-10 reviews loaded from the page).

Parameters:

url (required) - Fiverr gig URL or path

Returns: List of reviews with buyer name, country, rating, date, and text.

`list_categories`

List all available Fiverr category slugs for use with search_gigs.

Returns: List of category objects with slug and name.

Workflow Examples

Finding a freelancer:

list_categories() - see available categories
search_gigs("3D character modeling") - browse results
get_gig_details(url) - check pricing tiers (use URL from search results)
get_seller_profile(seller_name) - review their profile (use seller_name from search results)
get_gig_reviews(url) - read reviews

Limitations

Reviews - only the first page of reviews is available (Fiverr loads more via AJAX which requires authenticated requests)
Rate limiting - Fiverr may block rapid requests. A 2-second minimum delay is enforced between requests (configurable via RATE_LIMIT_DELAY)
Data freshness - all data is scraped from public pages in real-time, not cached

How It Works

This server extracts structured data from Fiverr's public pages by reading the Perseus SSR data blob (<script id="perseus-initial-props">) that Fiverr's frontend framework embeds in every page. Uses curl_cffi for browser TLS fingerprint impersonation to handle Cloudflare protection, with automatic retry and fingerprint rotation.

Responsible Use

This tool is intended for personal use - finding freelancers, comparing gigs, and reading reviews through an AI assistant. Please:

Do not use for mass data harvesting or building databases of seller information
Do not use for automated competitive monitoring at scale
Respect Fiverr's infrastructure by keeping the default rate limit
Be aware that web scraping may violate Fiverr's Terms of Service

Development

git clone https://github.com/KyuRish/fiverr-mcp-server.git
cd fiverr-mcp-server
uv sync
uv run fiverr-mcp-server

License

MIT

Available Tools

5 tools

get_gig_detailsA

Get full details of a Fiverr gig including all pricing tiers (Basic/Standard/Premium).

All prices in USD. Use the seller username from results with get_seller_profile() for more seller info.

Args: url: Fiverr gig URL (e.g. "https://www.fiverr.com/username/gig-slug") or path ("username/gig-slug")

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	No
`tags`	No
`error`	No
`title`	No
`rating`	No
`seller`	No
`category`	No
`metadata`	No	Gig attributes like programming language, tools used
`packages`	No	Pricing tiers (Basic/Standard/Premium)
`description`	No
`sub_category`	No
`reviews_count`	No
`orders_in_queue`	No

TDQS

A4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It only adds that prices are in USD and URL format, but omits whether the tool is read-only, has rate limits, or requires authentication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences, with purpose first, then a contextual note on currency, and finally parameter details. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to detail return values. It covers purpose, parameter format, and a hint about seller info. However, missing behavioral details (e.g., error cases) keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description significantly adds value by explaining the URL format with examples, distinguishing between full URL and path. This compensates for the lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Get' and resource 'full details of a Fiverr gig', explicitly listing included elements (pricing tiers). This clearly distinguishes it from siblings like get_gig_reviews and search_gigs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The suggestion to use get_seller_profile() for more seller info provides context on when to combine tools, but lacks explicit when-not-to-use or comparison with other tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_gig_reviewsA

Get reviews for a Fiverr gig. Returns the first page of reviews only (typically 5-10 reviews).

Args: url: Fiverr gig URL (e.g. "https://www.fiverr.com/username/gig-slug") or path

ParametersJSON Schema

Name	Required	Description	Default
`url`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`url`	No
`note`	No	Limitation notice
`error`	No
`reviews`	No

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses that only the first page (5-10 reviews) is returned, but does not mention authentication, rate limits, or other behavioral aspects like error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that are front-loaded and efficient. The note about first page and the args format provide necessary detail without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple single-parameter tool with an output schema, the description is almost complete. It covers input format and a key pagination behavior. Minor gap: no mention of error cases or prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter 'url' is explained with a format example and allowance for path, adding meaning beyond the schema's type-only definition. This compensates for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get reviews for a Fiverr gig' using a specific verb and resource. It also distinguishes from siblings like get_gig_details or get_seller_profile by focusing exclusively on reviews.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (when you need reviews) but does not explicitly state when not to use or mention alternatives. Context from sibling tools provides some differentiation, but no explicit guidance is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_seller_profileA

Get a Fiverr seller's profile including bio, languages, certifications, and gig listings.

Use the seller_name from search_gigs() results as the username here.

Args: username: Seller's Fiverr username (e.g. "johndoe")

ParametersJSON Schema

Name	Required	Description	Default
`username`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`bio`	No	Short one-liner tagline
`url`	No
`gigs`	No
`error`	No
`location`	No
`username`	No
`languages`	No
`description`	No	Full profile description/about text
`hourly_rate`	No	Hourly rate in USD
`is_verified`	No
`display_name`	No
`member_since`	No	e.g. Jan 2023
`response_time`	No
`certifications`	No
`approved_gigs_count`	No

TDQS

A4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits but only mentions the action 'get' without discussing read-only nature, authentication requirements, rate limits, or any side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise: two sentences and an argument line. Every sentence adds unique value without redundancy, making it efficient for an AI agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter and an existing output schema, the description covers the essential aspects: what the tool returns and how to get the input. Slightly lacking in error handling or usage context, but adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaning by explaining the 'username' parameter, its format (e.g., 'johndoe'), and deriving it from search_gigs(). This compensates well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves a seller's profile and lists specific contents (bio, languages, certifications, gig listings), distinguishing it from sibling tools that focus on gig details or search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on sourcing the username from search_gigs() results, indicating a logical sequence. However, no when-not-to-use or alternative tools are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_categoriesA

List all available Fiverr category slugs. Use these slugs with the category parameter in search_gigs().

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present. Description correctly indicates a read-only operation (listing) without side effects. However, it does not detail any potential limitations or return format beyond slugs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no wasted words. Purpose and usage are immediately clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, a simple output, and the presence of an output schema, the description adequately covers all necessary information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has zero parameters, so description has no need to add param info. Baseline score of 4 applies as there is nothing to improve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it lists all available Fiverr category slugs, explicitly naming the resource and action. It differentiates from siblings like search_gigs() by specifying the output is slugs for use with that tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on using the output slugs with the category parameter of search_gigs(). Does not explicitly mention when not to use, but the context implies it is only for retrieving slugs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_gigsA

Search Fiverr gigs by keyword. Returns up to 48 gigs per page. All prices in USD.

Use the gig URL from results with get_gig_details() for full pricing. Use the seller_name from results with get_seller_profile() for seller info.

Args: query: Search query (e.g. "logo design", "python developer") category: Category slug to filter by (leave empty for all categories) min_price: Minimum price in USD max_price: Maximum price in USD seller_level: Filter by seller level sort_by: Sort order for results page: Page number (starts at 1)

ParametersJSON Schema

Name	Required	Default
`page`	No
`query`	Yes
`sort_by`	No	relevance
`category`	No
`max_price`	No
`min_price`	No
`seller_level`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`gigs`	No
`page`	No
`error`	No
`query`	No
`has_more`	No
`total_results`	No

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present, so description carries full burden. Discloses pagination (up to 48/page), currency (USD), and the read-only nature of search. Could mention rate limits but sufficient for agent understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact, well-organized with intro, usage tips, and structured Args list. Every sentence adds value with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, multiple enums, output schema present, and sibling tools, the description fully equips the agent to select and use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema coverage metric, the 'Args' section explains all seven parameters with examples and meaning, adding significant value beyond schema enums and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches Fiverr gigs by keyword, specifies result behavior (up to 48 per page, USD prices), and distinguishes itself by directing use to sibling tools for details or seller info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on using results with get_gig_details and get_seller_profile, and includes parameter examples. Lacks explicit 'when not to use' but context implies alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct aspect of Fiverr data: gig details, reviews, seller profile, categories, and search. There is no overlapping functionality.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with underscores: get_gig_details, get_gig_reviews, get_seller_profile, list_categories, search_gigs.

Tool Count5/5

Five tools is appropriate for a focused server that covers search, retrieval of gigs, reviews, seller info, and category listing without being too sparse or bloated.

Completeness4/5

The server covers key read operations for Fiverr discovery but lacks write operations (e.g., creating gigs or orders). It is complete for its apparent purpose of inspecting Fiverr data.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Related MCP Connectors

MCP Finder B
io.github.c5huracan
Find the right MCP server for your task. 4,500+ servers ranked by community trust.
Search Developer Tools
3
nü people Job Server A
io.github.nu-people
Public MCP server for discovering open jobs. Search, filter, and get application links.
Search
52
H-Index A
ai.xr-utilities
Capability registry for the agentic economy. Semantic search over verified MCP server listings.
Search Documentation Access
32
Prowl MCP
chat.prowl
MCP server: 447 pay-as-you-go research tools (SEO, ads, SERP) + verified prowl_analyze reports
Marketing Search Research & Data
2

Related MCP Servers

trading212-mcp-server
Finance
KyuRish
A
license
A
quality
B
maintenance
MCP server for the Trading 212 API. Provides 28 tools for portfolio management, trading, pies, dividends, market data, and analytics.
Updated 16 days ago (2026-08-20 07:45 UTC)
28
6
MIT
mcp-dashboards
Data Platforms Data Visualization Finance
KyuRish
A
license
A
quality
B
maintenance
Renders 45+ interactive chart types, dashboards, and KPI widgets directly inside AI conversations. Supports drill-down, live API polling, 20 themes, and one-click export to PNG, PowerPoint, and A4 documents.
Updated 13 days ago (2026-08-23 08:25 UTC)
40
250
44
Functional Source , Version 1.1, MIT Future
Marketplace Search MCP
Search E-commerce & Retail Web Scraping
lulzasaur9192
A
license
B
quality
C
maintenance
MCP server for searching marketplaces (TCGPlayer, Reverb, Thumbtack), verifying professional licenses (contractor, nurse), and looking up PSA card grading data. Returns real-time pricing, listings, and verification results.
Updated 5 months ago (2026-03-29 00:16 UTC)
22
108
4
MIT
kwork-mcp
E-commerce & Retail Communication Project Management
simonether
A
license
A
quality
B
maintenance
MCP server that exposes 25 tools for the Kwork freelance marketplace — browse projects, submit offers, manage orders, send messages, and more.
Updated a month ago (2026-07-28 11:21 UTC)
28
3
MIT

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KyuRish/fiverr-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server