Fix with AI Agents
Your AI agent ships the fixes. We check they worked.
Connect AnswerPeek to Claude, Cursor, Codex or VS Code over MCP and put your agent to work on your AI visibility. It sees where you lose AI answers, pulls the brief, makes the change in your site and asks us to re-measure.
On every plan, trial included · no API key
- In every planThe trial too. No extra charge for connecting an agent.
- No API keySign in and approve, like any app. Revoke it in Settings.
- You set the limitsRead only, or let it move fixes and verify them.
- Grounded in real answersEvery brief points to what the engines said and cited.
One question in. A shipped fix out.
MCP lets your assistant call AnswerPeek directly, so it works from your live data, not a copy-paste.
- 1
Ask in plain words
“Where am I losing to competitors?” No dashboard to open, nothing to export.
- 2
It reads your live data
Your score, the prompts you lose, the rivals named instead and the sources the engines cite.
- 3
It ships the fix
The brief says what to change, on which page, for a codebase or a CMS. Your agent writes it.
- 4
We check it worked
AnswerPeek re-reads the page and asks the engines again, so you see whether the fix holds.
Connected in three steps.
Pick your client. Tell it where the server is, sign in once, then ask.
- 1
Add the server once
Run this in any project. It is stored per user, so you only do it once.
Terminalclaude mcp add --transport http answerpeek https://www.answerpeek.com/mcp
- 2
Authenticate
Run /mcp, pick answerpeek, and approve the permissions in the browser tab that opens.
In Claude Code/mcp
- 3
Ask it to do the work
Ask for the fix board, then for a brief. It reads your repo and the brief in the same conversation.
Another client? Anything that speaks Streamable HTTP with OAuth 2.1 works. Point it at https://www.answerpeek.com/mcp. There is no client id to create. Every tool and permission is in the MCP server docs.
Eleven tools. Your agent picks the right one.
Eight read your data. Two move fixes on the board. One re-measures a fix, and only that one spends a check.
guideHow the server works and the order to call things in.Readlist_workspacesThe workspaces you can work in: your own and any agency's you joined.Readlist_projectsEvery brand you track, with its score and how fresh it is.Readget_visibilityOne brand's standing: score, usual swing, each engine, the prompts it loses, rivals named instead.Readlist_focus_areasA brand's directions: Core and each focus area, with their latest score.Readlist_fixesThe fix board, biggest projected gain first. All of it, or one focus area's.Readget_fix_briefWhat to actually do about one fix, for a codebase or for a CMS.Readget_citationsWhich domains the engines cite, and what kind of place each is.Readupdate_fix_stageMove a fix between columns, or take it off the board.Writereport_blockedRecord why a fix could not be done.Writeverify_fixRe-crawl the page and re-measure. Uses one check.Verify · 1 check
You decide what it can touch.
Your client sends you to AnswerPeek to sign in and approve, like any other app. Grant only what you want.
- Read your dataProjects, prompts, runs, fixes and citations. Every connection needs this one.
- Move fixes on the boardChange a fix stage or take it off the board. Nothing else is writable.
- Verify a fixSpends a checkRe-crawl the page and re-measure the answer.
It cannot create projects, add prompts or start a run. Revoke any connection in Settings → MCP.
Connect an application
Signed in as maya@northpeak.co. If you approve, this application will be able to:
You can revoke this connection any time in Settings → MCP.
Works where you already work.
MCP and AI agent questions.
The Model Context Protocol is an open standard that lets an AI assistant call outside tools. Once AnswerPeek is connected, your assistant reads your visibility data and acts on it, instead of you copying numbers into a chat window.
Claude on the web, desktop and mobile, Claude Code, Codex, Cursor, VS Code with Copilot in agent mode, and anything else that speaks Streamable HTTP with OAuth 2.1. There is no client id to create.
No. Your client sends you to AnswerPeek to sign in and approve, like any other OAuth app, and gets a token for this server alone. Nothing to store or rotate, and you can revoke it from Settings at any time.
Only what you approved, and the list is short: move a fix between columns, take one off the board, record why one was blocked, and re-verify. It cannot create projects, add prompts or start a run. A read-only connection is a normal choice.
Yes. Every brief comes for a codebase or for a CMS, so an assistant like Claude can walk you through the change in your site editor, step by step.
Yes, with you in the loop. Connected over MCP, the agent reads where you lose AI answers, pulls the brief for a fix and makes the change in your codebase, or walks you through it in your CMS. AnswerPeek then re-reads the page and asks the engines again, so you see whether it worked.
It spends one check from your monthly allowance, because it re-runs the prompt against the engines. That is why verifying is a separate permission from moving fixes: you never have to grant the one that costs to get the one that doesn't.
Yes. The agent sees every workspace you belong to, your own and any agency's you joined. On the consent screen you approve one workspace or all of them.
Yes, on every plan including the trial. There is no separate charge for connecting an AI tool.