Finds influencers/creators by keyword or curated niche across seven platforms, returning one flat row per creator per platform.
Search by keywords (each searched on every selected platform) or by one of eight curated niche keyword sets (custom, personal_finance, business_marketing, health_fitness, beauty_skincare, parenting_family, food_cooking, travel, tech_ai), capped by max_keywords_per_niche (1–60, default 10).
Target platforms: TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts (no X, Facebook pages, or LinkedIn).
Filter by follower range (follower_min default 5000, follower_max default 500000); creators with unknown counts are kept.
Cap result size with max_creators (default 200) and max_creators_per_keyword (default 20), and tune batch_size for speed.
Bias results by search country (any, US, GB, CA, AU, IE, NZ, DE, FR, NL, SE).
Bound runtime per keyword/platform with keyword_time_budget_secs (10–600, default 60) so runs finish as SUCCEEDED.
Get one flat row per creator per platform with handle, profile URL, display name, follower count, source search, stable creator_id, and similar creators from the same keyword cluster.
Read row_status and error_reason on every row to distinguish blocked/failed creators from gaps.
Contribute found public records to a shared creator/agency pool (contribute_to_shared_pool, on by default, free, no account data sent); disable to read-only.
Discovery only — it does not read bios, emails, or link-in-bio pages (those are separate suite actors).
Requires an APIFY_TOKEN and Apify credits ($0.001 per run + $0.007 per creator returned; empty searches charge run start only).
Optional max_charge_usd cap; us_only is accepted but has no effect here.
Allows discovering Instagram influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Allows discovering Pinterest influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Allows discovering Threads influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Allows discovering TikTok influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Allows discovering Twitch influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Allows discovering YouTube influencers by keyword or niche, returning handles, profile URLs, and follower counts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Influencer Finder MCP Server find budget travel influencers on TikTok with 10k+ followers"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for the Mamba Labs Influencer Finder actor on Apify.
Keywords or a curated niche in, influencer handles out, one flat row per creator per platform.
npx -y @mambalabsdev/mcp-creator-finder{
"mcpServers": {
"mamba-creator-finder": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-creator-finder"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get an Apify token at console.apify.com/account/integrations.
Related MCP server: Influship MCP
find_influencersFind influencers by keyword or niche across seven creator platforms, with follower counts.
Input | Type | Required | Notes |
| array | no | Search phrases, one per line, for example "budget travel" or "meal prep coach". Each keyword is searched on each platform. Use |
| string | no | Loads a curated set of search keywords for the niche (about 60 per niche, measured in the September 2026 pre-research). |
| integer | no | How many keywords from the niche set to search. 1 to 60. Default |
| array | no | Which platforms to search, and which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. Supported: TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts. |
| integer | no | Cap per search. Search engines honor the site: filter for the first page or two only, so 20 to 30 per keyword with more keywords beats deep paging. Default |
| integer | no | Hard cap on rows returned, so a broad niche cannot run away. Default |
| integer | no | Drop creators whose follower count is known and below this. A creator whose count the search did not show is kept, so a later profile read can fill it. Default |
| integer | no | Drop creators whose follower count is known and above this. Default |
| boolean | no | Launch scope is US creators. Discovery carries no country signal, so country_guess is null on every row of this actor and this field changes nothing here. It is accepted so the same input runs unchanged on the Influencer Lead List Builder. Default |
| integer | no | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. |
| integer | no | Wall time allowed for each keyword on each platform, in seconds. A hung search page is given up at the budget, so a full niche set finishes as a SUCCEEDED run. 10 to 600. Default |
| string | no | Runs the search engine queries from this country so results lean to creators there: |
| boolean | no | On by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from. Only public data already in the returned rows is sent, and a contribution is not charged. Set false to read the pool and write nothing. Default |
| number | no | Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit to rely on the maximum cost per run set in Apify. |
Nothing is required. Influencer Finder answers a run with no usable input with a row carrying row_status and error_reason rather than failing, and the tool mirrors that.
Influencer Finder is pay per event on Apify. Every price below is flat across every tier: FREE, BRONZE, SILVER, GOLD, PLATINUM, and DIAMOND.
Event | Charged for | Price | Fires when |
| Actor start | $0.001 | Once per run, on start. Covers the run overhead. |
| Apify actor start | not charged | Apify's synthetic start event. This actor prices its own |
| Creator found | $0.007 | Once per creator row returned by keyword or niche discovery with a handle and a profile URL. A search that returns nothing charges nothing. |
Every row carries row_status and error_reason. A creator the actor could not read comes back as a row saying why, not as a gap in the list, so an absence is readable rather than inferred. Filter on row_status before loading a table.
The run contributes the records it finds to a shared creator and agency pool that all users of this actor read from. What one run finds, the next run can read.
The toggle is contribute_to_shared_pool. It is on by default. Set it to false and the run still reads the pool and writes nothing to it.
What this actor contributes. The creator ID, platform, and handle of every creator it finds. No profile detail, because this actor reads none.
Only public data that is already in your own output. Every field written to the pool is a field this run returned to you, read from a page the platform or the creator publishes to anyone without a login. Nothing from your Apify account, your input list, your API keys, or your own notes is sent. A contribution never deletes anything from the pool.
What a contribution is labeled with. The actor ID, the run ID, the pool key issued to the actor build, and a hash of the calling IP address, used for the rate limit and nothing else. Your Apify account and your user ID are not recorded.
Contributing is free. No event is charged for a write to the pool. If the pool is unreachable the run finishes as normal, the rows are dropped, and the run log says so.
Actor ID tpkedmloIIWtXx6sg. The wrapper calls the actor by that immutable ID rather than by its Store slug, so a Store rename never breaks it.
Actor | Actor ID | MCP server |
| ||
| ||
| ||
| ||
| ||
|
Built by Mamba Labs.
Searches TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts for creators matching your keywords or one of eight curated niche keyword sets, then filters them to a follower range. Returns one flat row per creator per platform with handle, profile URL, display name, follower count, the search that found them, a stable creator_id, and similar creators from the same keyword cluster. Discovery only: it does not read bios, emails, or link in bio pages, which is what Influencer Profile Scraper and Link in Bio Scraper and Newsletter Detector do. Every row carries row_status and error_reason, so an absence is readable rather than silent. Charges $0.001 per run plus $0.007 per creator returned; a search that returns nothing charges the run start only. Contributes the public records in its rows to a shared creator pool, free and on by default; contribute_to_shared_pool explains it and turns it off. A run that does not succeed is returned as an error with its run ID and status. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
| Name | Required | Description | Default |
|---|---|---|---|
| niche | No | Loads a curated set of search keywords for the niche (about 60 per niche, measured in the September 2026 pre-research). `max_keywords_per_niche` caps how many are used. Leave as custom to search only your keywords. Default: "custom". | |
| country | No | Runs every search engine query from this country with the matching Google country setting, so results lean to creators there. any rotates the exit country. Default: "any". | |
| us_only | No | Launch scope is US creators. Discovery carries no country signal, so country_guess is null on every row of this actor and this field changes nothing here. It is accepted so the same input runs unchanged on the Influencer Lead List Builder, where it acts at the profile stage. Default: true. | |
| keywords | No | Search phrases, one per line, for example "budget travel" or "meal prep coach". Each keyword is searched on each platform. Use `niche` instead to load a curated keyword set. | |
| platforms | No | Which platforms to search, and which platforms a bare @handle is looked up on. A full profile URL carries its own platform and ignores this. Supported: TikTok, Instagram, YouTube, Pinterest, Twitch, Threads, and podcasts. Not X, not Facebook pages, not LinkedIn. | |
| batch_size | No | Rows fetched at once. Leave empty for the measured per platform default; the measurement is in the README. Higher is faster and, above the measured point, loses rows. | |
| follower_max | No | Drop creators whose follower count is known and above this. Default: 500000. | |
| follower_min | No | Drop creators whose follower count is known and below this. A creator whose count the search did not show is kept, so a later profile read can fill it. Default: 5000. | |
| max_creators | No | Hard cap on rows returned, so a broad niche cannot run away. Default: 200. | |
| max_keywords_per_niche | No | How many keywords from the niche set to search. 1 to 60. Default: 10. | |
| keyword_time_budget_secs | No | Wall time allowed for each keyword on each platform, in seconds. A search page that hangs is given up at the budget, and the run starts no new keyword when its own timeout is closer than one budget, so a full niche set finishes as a SUCCEEDED run instead of timing out. 10 to 600. Default: 60. | |
| max_creators_per_keyword | No | Cap per search. Search engines honor the site: filter for the first page or two only, so 20 to 30 per keyword with more keywords beats deep paging. Default: 20. | |
| contribute_to_shared_pool | No | On by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data already in the returned rows is sent, never your Apify account, your input list, or your API keys, and a contribution is not charged. Set false to read the pool and write nothing. Default: true. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds material behavior the annotations cannot: exact pricing model ($0.001 per run + $0.007 per creator, run-start-only charge on empty results), the shared creator pool contribution that is on by default, APIFY_TOKEN and credit requirements, row_status/error_reason on every row, and error-with-run-ID on failure.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the searched platforms, the matching logic, and the returned columns before moving to scope exclusions, pricing, and pool behavior. Dense but nearly every sentence carries actionable detail; it is slightly overstuffed for a description, keeping it out of the top tier.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description still enumerates the returned fields, explains row_status/error_reason, and covers billing, auth, and failure behavior for a 13-parameter tool. An agent has everything it needs to invoke this correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3 and the schema already carries the per-parameter detail. The description reinforces the follower-range filtering and niche-set behavior, but adds little syntax or format guidance beyond the schema (its us_only note is one exception). No credit above baseline is warranted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (searches TikTok/Instagram/YouTube/Pinterest/Twitch/Threads/podcasts for creators matching keywords or a curated niche set), then narrows by follower range. It also names exactly what it returns per row (handle, URL, display name, followers, source search, creator_id, similar creators). An agent can distinguish this discovery tool from any profile-reading tool without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly frames the tool as 'Discovery only' and names the alternatives (Influencer Profile Scraper, Link in Bio Scraper, Newsletter Detector) for bio/email/link-in-bio needs. It also describes when a search yields nothing and how that is surfaced, so the agent knows both the right and wrong uses.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.1.1find_influencers3 fields changedInput schema / properties / contribute_to_shared_poolAdded value: +{
+ "description": "On by default. Contributes the public records this run finds to a shared creator and agency pool that all users of this actor read from, so a later run reads what this one found. Only public data already in the returned rows is sent, never your Apify account, your input list, or your API keys, and a contribution is not charged. Set false to read the pool and write nothing. Default: true.",
+ "type": "boolean"
+}Input schema / properties / countryAdded value: +{
+ "description": "Runs every search engine query from this country with the matching Google country setting, so results lean to creators there. any rotates the exit country. Default: \"any\".",
+ "enum": [
+ "any",
+ "US",
+ "GB",
+ "CA",
+ "AU",
+ "IE",
+ "NZ",
+ "DE",
+ "FR",
+ "NL",
+ "SE"
+ ],
+ "type": "string"
+}Input schema / properties / keyword_time_budget_secsAdded value: +{
+ "description": "Wall time allowed for each keyword on each platform, in seconds. A search page that hangs is given up at the budget, and the run starts no new keyword when its own timeout is closer than one budget, so a full niche set finishes as a SUCCEEDED run instead of timing out. 10 to 600. Default: 60.",
+ "maximum": 600,
+ "minimum": 10,
+ "type": "integer"
+}v1.0.0find_influencersScored across 1 tool
With only one tool exposed, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The description's references to sibling servers (Profile Scraper, Link in Bio Scraper) are out of scope for this set and do not create internal ambiguity.
The single tool uses a clean verb_noun snake_case pattern (find_influencers) that directly reflects its action and resource. There are no competing conventions to clash with.
One tool for a whole server is thin even for a narrowly scoped discovery service; a user has no way to list niches, retrieve a run's results by ID, or look up a creator by the creator_id the tool returns. The single tool is rich, but the surface is borderline minimal.
The discovery step is well covered across many platforms and the tool honestly declares its boundary (no bios, emails, or link-in-bio), which are handled by separate servers. However, within this server there is no follow-up operation: no pagination, no fetch-by-run-id, no lookup by the advertised stable creator_id, and no way to act on the shared pool it contributes to.
Find and analyze influencers with creator search, lookalikes, profiles, posts, and transcripts.
Find Instagram creators and leads by niche, city, follower range or lookalike accounts.
Search 455M+ Instagram, TikTok and YouTube creators and analyze influencers from your AI assistant.
Search 300M+ TikTok, Instagram and YouTube creators by brief; check fake followers; get emails.
