Perplexity Web / App Verification
Perplexity does not currently document a confirmed end-user flow for connecting an external remote MCP server such as Codebase inside the Perplexity web or mobile app. This page is a verification checklist rather than a finished setup guide.
The currently confirmed Perplexity docs describe how to connect Perplexity’s own MCP server to other MCP clients. Whether the Perplexity web or mobile app exposes a user-facing UI for external remote MCP servers still needs direct product verification.
Last verified: 2026-04-17
Screenshots are replaced automatically when you update the matching files under frontend/public/docs/apps/perplexity.
Before you start
- You need an active Perplexity account and access to the exact product surface you plan to test.
- Before claiming support, verify whether that surface allows external tools, apps, integrations, or MCP connections at all.
- Until support is confirmed, do not present this page as a general end-user setup guide.
Connection steps
Look for an external connection entry point in the Perplexity UI
Check whether the current product surface actually exposes something like Settings, Integrations, Apps, Tools, or MCP. If no such entry point exists, record that this surface does not support external remote MCP connections.
This step is specifically about product verification. If the menu does not exist, stop here.
Replace this file with your screenshot
Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.
frontend/public/docs/apps/perplexity/01-entry.pngCheck for an external remote MCP or custom integration flow
Verify whether the UI allows you to enter an external server URL or configure a custom integration. Perplexity’s official MCP docs cover the opposite direction, so this still requires direct UI validation.
If no such form exists, keep this document in the unsupported or unverified state.
Replace this file with your screenshot
Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.
frontend/public/docs/apps/perplexity/02-open-connect.pngCapture the connected state only if support is confirmed
Only after a real connection flow is confirmed should you document the connected state, invocation pattern, and test prompt for Codebase.
Until you have a real post-connection screenshot, keep the placeholder and leave the page marked as manually verified.
Replace this file with your screenshot
Put the final screenshot in the exact path below. The docs page will start rendering it automatically without any code changes.
frontend/public/docs/apps/perplexity/03-complete.pngTest checklist
- Record whether the Perplexity UI exposes any external connection or custom integration entry point.
- Record whether it accepts an external remote MCP URL.
- If it is unavailable, mark it unsupported. If it exists, note whether it is beta or preview only and what plan is required.
Troubleshooting
- First confirm whether the linked Perplexity docs describe inbound or outbound MCP support.
- If the actual product UI has no connection menu, do not claim that external MCP is supported.
- Until support is verified, keep this page positioned as an internal validation note rather than a public how-to.
If you need to review connection state or permissions again, also check the Connected apps page.