What is the Favikon MCP Server?
It's a connector that gives AI assistants direct access to your Favikon workspace. Instead of navigating the app, you can ask your assistant to find creators in a niche, build a shortlist, launch a campaign, or check what a tracker picked up this week — and it calls the same APIs the product runs on.
It exposes 63 tools across these areas:
Account & workspace – check who you're authenticated as, remaining credits, workspace members
Discovery – semantic creator search, content search, lookalikes, full profiles, handle lookup, price estimates, brand fit
Rankings – Favikon's leaderboards by country, platform, and topic
Campaigns – create/update campaigns, attach a brand, launch/pause/resume
Campaign roster – add, remove, and move creators between stages
Conversations – read/send messages, list connected channels, generate connection links
Automation – build, edit, preview, and activate outreach sequences
Content & analytics – campaign content feed/gallery/calendar, campaign performance
Lists – create lists, manage members, add comments
Segments – define, count, and commit filter-based creator segments
Contacts & enrichment – CRM queries, email finding, contact enrichment
Trackers – watch a brand/hashtag/topic over time
Credit mode – controls whether credit-spending tools ask for confirmation first
Delete – a single confirmation-gated tool to remove campaigns, lists, trackers, segments, or purge contacts
How do I set it up?
Claude Code: claude mcp add --transport http favikon https://mcp.favikon.com/mcp
Then run /mcp in a session to confirm the connection, and ask "get my current user" to verify.
Claude, Cursor, and other clients with a JSON server definition:
{
"mcpServers": {
"favikon": {
"type": "http",
"url": "https://mcp.favikon.com/mcp"
}
}
}
Clients with a connector UI: paste https://mcp.favikon.com/mcp into the "Add custom connector" dialog.
On first use, the client opens a browser window so the user can sign in to Favikon and authorize access.
How does authentication work?
Two methods:
OAuth (default for interactive clients) — the assistant discovers the login flow automatically and the user's token carries their workspace and role permissions.
API key (for automation/CI with no browser) — generated from account settings, sent as a bearer token. Keys don't expire; users should revoke a leaked key from the same screen and never commit it to version control, since it grants full workspace access including credit spend and outreach sending.
Does the MCP grant extra access?
No. It inherits the user's existing Favikon permissions exactly — no new access is granted. Users only reach workspaces they can already open in the app, and role limits apply the same way they do in the UI. Data is isolated per user: two people on the same server never see each other's data.
Does it use credits?
Some tools do — email finding, contact enrichment, and other enrichment paths. These respect credit mode:
Cautious (default) — previews the cost and waits for confirmation before spending
Auto — spends directly (switching to this requires explicit confirmation)
Search, rankings, profiles, price estimates, and brand fit use credits just like they do when using these features directly on the platform.
Here's the credit breakdown:
Creator Search: 1 Favicoin per search (25 results)
Content Search: 1 Favicoin per search (25 results)
Lookalike: 2 Favicoins
Radar: 2 Favicoins
Rankings: Free
Profile Preview: 1 Favicoin
Full Profile Lookup: 3 Favicoins, this unlocks full access to a creator's profile (audience analytics, contact info, performance history, engagement quality) for 30 days, so you can revisit it during that period without spending more credits.
Item | Detail |
Session lifetime | Idle sessions are evicted after 30 minutes; clients reconnect automatically. |
Credit spend | Enrichment tools draw on workspace credit balance, governed by credit mode. |
Destructive actions | Deletes are confirmation-gated. Removing contacts already in a campaign needs an explicit force flag. |
Outreach sending | Messages sent through the MCP are real — they go out from connected accounts and follow the same platform limits as the app. |
Data sharing | Tool results are sent to whichever AI provider powers the user's client. Recommend reviewing that provider's data handling before connecting an account with sensitive CRM data. |
Async enrichment |
|
Troubleshooting
"Tools return an authentication error" The session expired or the key was revoked. Reconnect the server to trigger a fresh login, or generate a new API key.
"The server connects but no tools appear" Most clients load the tool list once per connection. Disconnect and reconnect (in Claude Code, run /mcp) so the catalog reloads.
"A creator can't be found" Search is semantic and returns approximate matches. To resolve one specific account, use find_creator_by_handle with the profile URL or @handle rather than a name search.