Skip to main content
Add Fandom’s MCP server to your client once, then ask about audiences, inclusion lists, projects, Trends and campaigns in plain words. It uses your Fandom account.
You sign in on super.fans, Fandom’s sign-in service. When it asks, pick your Fandom organization.

Connect

  1. Go to Customize → Connectors, click Add and choose Add custom connector.
  2. Name it Fandom, paste the address above and click Continue.
  3. Keep the sign-in settings Claude detects (Register automatically), then click Add.
  4. Click Connect, sign in and click allow.
On Team and Enterprise plans, an owner adds it once under Organization settings → Connectors → Add → Custom → Web, then each person connects. See Claude’s guide.
That’s it. Nobody has to approve it, and it works right away. Next, see what you can ask, or the full list of tools.
Use www.fandom.ai/mcp. The similar docs.fandom.ai/mcp only searches these docs.

What you can do

Ask the way you’d say it

  • Names are enough. Every tool takes channel names, @handles, YouTube channel or video links, websites, links to Fandom pages, and the names of your lists, projects, reports, brands, audiences and campaigns. Your client doesn’t need ids.
  • Each answer says how it read you. It starts with “Read your request as: …” when it matched a name or adjusted something, such as a size that was too big.
  • Big jobs reply “working”. Your client checks back with get_job until the answer is ready. List runs and project builds take minutes; ask “is it ready?” any time.
  • Your current workspace is used. If you belong to several, Fandom uses the one you last used from that app. Say another workspace’s name to switch.

Who can do what

  • It acts as you. Your workspace role limits what your client can do with campaigns, audiences, brands, data stores and Google Ads accounts. Audience Exploration, inclusion lists, projects and Trends are open to every member, including saving a map’s channels as an audience or a campaign.
  • It can read and write by default. Admins can limit an app to read only under Settings → API & MCP → Connected apps, where they can also see who connected it, rename it or disconnect it. A read-only app can still map, read and write reports; it can’t save or change things.
  • No ad spend. Google Ads campaigns are always created paused. Nothing spends until someone turns the campaign on in Google Ads, and targeting reaches Google Ads when someone syncs the campaign in Fandom.
  • Some research costs. Inclusion list runs, project builds, project lenses and reports, and Trends spend AI or start paid runs. Their tools say so, and Fandom tells your client to ask you first. Maps, splits, channel details and audience reports run freely.
Each person can make 120 requests a minute from each app. Audience Exploration also has a workspace limit: 240 requests a minute, 2 analyses at once and 60 analyses an hour.

If something’s not working

Use an API key instead

For scripts, or clients that can’t sign in, send an API key as a header. Only workspace admins can create keys. A key’s scopes decide what it can do, not a person’s role, and it always works in the workspace it was made in.
The Claude Code command stores the key in its settings file. Use a key you can revoke, and revoke it under Settings → API & MCP if it leaks.