Brand Sponsor 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 from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. | |
| YOUTUBE_API_KEY | No | Optional. Your own YouTube Data API key; it is passed to the actor as youtube_api_key so the key never goes through the conversation. With it the actor searches YouTube for channels in the niche and reads up to 50 uploads per channel. |
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_brand_sponsorsA | Find brands with recent public proof of paid placement in a niche. Give a niche (for example health and fitness, beauty and skincare, food and beverage) and optionally audience keywords, seed YouTube channels, podcast feeds, or newsletters, and event sponsor pages. The actor reads public YouTube descriptions, podcast show notes, newsletter issues, event sponsor pages, partnership job posts, and brand creator program pages, and returns one row per brand domain (sighting count, last seen date, sources, creators or events sponsored, public contact, recency score) and one row per sighting (brand, domain, source, creator or event, date, evidence link, promo code, placement type, pitch angle). Instagram, TikTok, and the Meta Ad Library are not read. Input with nothing to run returns one free row whose error_reason starts with input_invalid:. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per brand row, per sighting row, and per run start. |
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
There is only one tool, so there is no risk of selecting between overlapping operations. Its purpose is clearly stated as brand sponsor discovery.
The single tool uses a clear snake_case verb_noun pattern: find_brand_sponsors. There are no conflicting naming conventions within the set.
The single tool fits the narrow discovery purpose, but a one-tool surface is inherently thin and limits the server to one operation. It is not a trivial tool, but the set is at the low end for an MCP server.
For a read-only brand sponsor discovery server, the tool covers the core search use case with rich inputs and outputs. Minor gaps remain around follow-up operations such as retrieving or managing individual brand records, but they are not required for the stated purpose.