Influencer Finder MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token (get it at https://console.apify.com/account/integrations) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_influencersA | 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; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored 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.