| name | perplexity |
| description | Ask Perplexity a question by driving Channing's logged-in Chrome session, and report its answer. Use when the user says "ask Perplexity", "what does Perplexity say", "run this past Perplexity", or wants a Perplexity-sourced answer or second opinion. Avoids the paid Perplexity MCP server. |
Perplexity via browser
Ask perplexity.ai questions through the browser instead of the paid MCP server.
Prerequisites
Use the claude-in-chrome tools — they drive Channing's own Chrome, where he is already
logged into Perplexity. Do not use agent-browser or WebFetch: they have no session and
will hit the logged-out page.
Asking
tabs_context_mcp, then tabs_create_mcp for a fresh tab.
navigate to https://www.perplexity.ai/search/new?q=<url-encoded question>.
The /search/new path auto-submits — no clicking needed. The URL rewrites to
/search/<uuid> once the thread exists.
wait ~8s, then get_page_text.
- If the answer is still streaming,
wait and re-read. It is complete when a
Follow-ups block and a trailing Sources / N block appear; a final paragraph that
stops mid-sentence means it is still generating.
Follow-ups
Stay in the same tab to keep thread context:
read_page with filter: interactive → find the bare textbox near the bottom
(the "Ask a follow-up" box, just above the Submit button).
left_click its ref, type the question, key: Return.
- Wait and
get_page_text as above.
get_page_text returns the whole thread every time, so extract only the text after the
last question — don't re-report earlier answers.
Reporting back
Attribute the answer to Perplexity and keep it distinct from your own knowledge; if you
disagree with it, say so separately rather than silently correcting it.
Citations come through as bare source names (britannica, +2) with no URLs. If Channing
needs the actual links, click the Links tab (tablist "Answer mode tabs") or pull the
hrefs from read_page.