Connect Peak Answer to Claude, ChatGPT, Cursor or any MCP client and ask it about your own AI visibility, or to audit a page, check a robots.txt or write a brief. Included on every plan.
Peak Answer MCP puts Peak Answer inside Claude, ChatGPT, Cursor or any MCP client. Ask your assistant how your AI visibility is moving, which questions you are losing, or to audit a page, without leaving the chat. It is included on every plan, and connecting takes one click on Approve.
Peak Answer MCP is included on every plan, and the free trial includes it too.
Sign up for Peak AnswerSettings, then Connectors, then Add custom connector. Name it Peak Answer, paste the URL below and press Connect. Peak Answer opens, you click Approve, and you are done.
Server URL
https://peakanswer.com/api/mcp
Add a custom connector from ChatGPT’s settings with the URL below, and choose OAuth if it asks how to sign in. Peak Answer opens, you click Approve.
Server URL
https://peakanswer.com/api/mcp
Add it in your terminal, then run /mcp inside Claude Code, pick peakanswer and approve in the browser.
terminal
claude mcp add --transport http peakanswer https://peakanswer.com/api/mcp
Add this to the MCP config file your client uses. Clients that support MCP sign-in open Peak Answer for you to approve.
mcp.json
{
"mcpServers": {
"peakanswer": {
"type": "http",
"url": "https://peakanswer.com/api/mcp"
}
}
}If yours cannot sign in, create a key in Settings, API key and MCP and send it as a header instead.
mcp.json with a key
{
"mcpServers": {
"peakanswer": {
"type": "http",
"url": "https://peakanswer.com/api/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}| Tool | What it does |
|---|---|
my_brand | The brand this connection is for: its domain, name, plan, how many questions are tracked, and which integrations are connected. Call this first whenever the user says 'my site', 'my website' or 'my domain', rather than asking them which site they mean. |
my_visibility | The signed-in brand's current visibility index, per-engine presence, and how it has moved. Use this when the user asks how they are doing, whether anything changed, or how they compare to their category. |
my_questions | Every buying question tracked for the signed-in brand, whether the brand is named, who wins it instead, and how volatile the answer is. Use this when the user asks what they are losing or which questions are worth attacking. |
my_question_history | The 90-day per-engine history for a single tracked question, including what the models actually said. Use this when the user asks about one specific question by name. |
my_actions | Everything Peak Answer currently recommends for the signed-in brand, with the reason, the expected effect and which engine it targets. Use this when the user asks what to do next. |
my_search_console | Google queries where the signed-in brand ranks between positions 5 and 15, from their connected Search Console. Use this when the user asks about quick SEO wins or what is close to page one. |
geo_audit | Peak Answer asks 10 real buying questions about your category and shows you who gets named. Takes a few minutes. |
answer_readiness_score | Checks individual pages for things like clean headings, lists, tables, schema, dates, sources, etc, and tells you if the page is ready to be cited by AI engines. |
check_ai_crawlers | Reads your robots.txt and tells you whether GPTBot, ClaudeBot, PerplexityBot, etc can reach your pages. |
generate_llms_txt | A short file telling AI what your site is and which pages matter. Adoption is still limited, so expect low impact, but it costs nothing. |
extract_entities | The brands, products, people and topics a model pulls out of your page, and the ones you meant to be there but are not. |
generate_prompt_set | Every buying question in your category, split by intent, ready to paste into whatever you track with. |
check_robots_txt | Every rule in your robots.txt, parsed the way crawlers parse it, plus the mistakes that quietly hide your site. |
check_sitemap | It finds your sitemap, counts what is in it, follows the index files, and flags the URLs that should not be there. |
validate_structured_data | Checks individual pages' JSON-LD blocks and tells you if your structured data is easily readable by AI engines. |
generate_faq_schema | Paste your questions and answers. Get valid FAQPage JSON-LD, the block models lift most often. |
trace_redirects | Every hop between the address you type and the page that loads. Chains and loops cost you crawl budget. |
find_broken_links | It follows the first 60 links on the page and reports the dead ones, with the status each one returns. |
check_page_speed | Google's Lighthouse performance score for the page on mobile, with the specific things holding it back. |
check_heading_structure | The full outline of your page and every place the hierarchy skips a level. Models read the outline first. |
check_meta_description | Do you have one, does it fit, and does it earn the click. |
check_readability | Reading grade, sentence length, passive voice and paragraph size. Dense prose is skipped by readers and skipped by models. |
generate_content_brief | A full brief for one keyword: angle, outline, questions to answer, entities to name, schema to ship. |
generate_semantic_keywords | The related terms, entities and questions a page has to cover before it reads as authoritative. |
We go fix it. Published, live, done, while you get on with the rest of your week.