Skip to main content
Prefer’s MCP server lets the AI assistants you already work in read your Prefer data. Ask in plain words how visible your brand is in ChatGPT, Gemini, Perplexity and Google’s AI answers, who leads among your competitors, which sources the engines cite, and what to fix first. Every answer comes from the same numbers as your console, with a link to the page it came from.

​
What your assistant can do

  • Visibility: visibility, share of voice, citation share and average position, overall and by engine, topic, persona or market, with the trend across runs.
  • Prompts and answers: the prompts you track, which ones name your brand, and what each engine answered.
  • Competitors and sources: the competitor leaderboard, where rivals win prompts you lose, and the sites the engines cite.
  • Actions and content: your Action Center, each action’s evidence and steps, and your Content Studio drafts.
  • Search Console: clicks and impressions by query or page, and where search demand and AI answers disagree, once Search Console is connected.
  • Skills: twelve ready-made workflows, such as a weekly pulse, a competitor radar and a client report, offered as prompts in assistants that support them.
Assistants read your data. They never change anything in Prefer: adding prompts, editing drafts and publishing stay in the app.

​
How it connects

The server address is:
Your assistant connects with an MCP key, a personal key you create on the MCP page, under Integrations in the left navigation. Step-by-step guides: Any other client that can send a header connects the same way: send Authorization: Bearer <MCP key> with every request to the server address.

​
Plans

AI assistant access is included in every Prefer plan, including earlier plans you may still be on, and during your free trial. If your workspace’s trial has ended or its plan is paused, assistants receive a plain message saying so until the workspace is active again.

​
Security and your data

  • A key reads one workspace, as the person who created it, with that person’s access. Someone who leaves the workspace can no longer read it with their key.
  • Prefer stores a fingerprint of each key, never the key itself, and shows the key once, when you create it.
  • Revoke a key on the MCP page, Keys tab, and the next request made with it is refused.
  • Text that comes from outside Prefer, such as quotes from AI answers and web pages, reaches your assistant marked as quoted material, so it is read as data rather than as instructions.

​
Numbers you can trust

The assistant reads the same measurements as the console, under the same rules. Share of voice is stated only when a run names brands at least 10 times, in the console and in every assistant answer, so a share never rests on a handful of mentions.