How does authorizing Tempreon work in Perplexity?

Adding the connector and authorizing it are two separate steps. When you add the custom connector you choose OAuth, which needs no client ID or secret because Tempreon supports dynamic client registration, and Streamable HTTP. Then you click the new Tempreon connector card, which opens a browser window with the consent screen to sign in and approve.

Where do I add the Tempreon connector in Perplexity?

On the web or the Mac or Windows desktop app, open Settings, then Connectors. Click Custom connector, choose Remote, and fill in the form with the name Tempreon, the MCP server URL, OAuth authentication, and Streamable HTTP transport. Check the acknowledgment box, then click Add.

I do not see the Custom connector option in Perplexity. Why?

Custom connectors require a Pro, Max, or Enterprise plan as of September 2026, so free accounts see only the built-in connector catalog. On Enterprise, the Allow members to add custom connectors toggle is off by default, so an admin has to turn it on before you can add your own. Once you are on a supported plan, the Custom connector option appears under Settings, Connectors.

Perplexity Setup — Docs

Overview

Perplexity is an answer engine that routes your questions through a roster of frontier models — GPT, Claude, Gemini, Grok, and Kimi among them, depending on your plan. Since March 2026 it has supported custom remote MCP connectors, which is how Tempreon plugs in.

Once connected, your AI loads your Core Imprint, searches your Knowledge Vault, and remembers what it learns — across every tool. And because Perplexity runs many models behind one interface, connecting Tempreon once gives every one of them your context: switch from GPT to Claude to Kimi mid-research and your identity and knowledge come along.

Quick path: Settings → Connectors → + Custom connector → Remote → paste the Tempreon URL → OAuth + Streamable HTTP → Add → click the connector card to authorize → toggle it on under Sources.

Availability note (as of September 2026): Custom connectors require a Pro, Max, or Enterprise plan (on Enterprise, members can't add their own until an admin turns on "Allow members to add custom connectors", which is off by default). Free accounts see only the built-in connector catalog. Perplexity documents custom remote connectors for the web and the Mac/Windows desktop apps, and doesn't document them for the Comet browser — set Tempreon up on the web or desktop. Note that Perplexity's older "Local and Remote MCPs" help article still says remote MCP is "coming soon"; that page is out of date and the custom-connector flow below is the current one.

Prerequisites

A Perplexity Pro, Max, or Enterprise account (on Enterprise, ask your admin to enable custom connectors)
A Tempreon account with at least one available Bridge slot
Your Tempreon MCP server URL (also shown in your Bridges dashboard)

Step-by-Step Setup

1. Open the Connectors settings

On the web or desktop app, open Settings → Connectors.

2. Add a custom connector

Click + Custom connector
Choose Remote
Fill in the form:
- Name: Tempreon
- MCP Server URL:

https://api.tempreon.com/functions/v1/tempreon-mcp/mcp

Authentication: OAuth — no client ID or secret needed; Tempreon supports dynamic client registration
Transport: Streamable HTTP

Check the acknowledgment box about custom connector risk
Click Add

3. Authorize the connection

Click the new Tempreon connector card. A browser window opens with the Tempreon consent screen — sign in if prompted, review the request, and approve.

4. Enable it as a source

Back in Perplexity, make sure the Tempreon connector is toggled on under Sources. Then ask something that touches your context to confirm it's live.

Troubleshooting

You don't see "+ Custom connector". Custom connectors require Pro, Max, or Enterprise as of July 2026. On Enterprise the feature is off by default — an admin has to enable it. Free accounts only get the built-in catalog.

The connector is added but Perplexity never uses it. Check that it's toggled on under Sources, and that you completed the authorization step by clicking the connector card.

Using Comet? Perplexity's Comet browser may not support custom connectors on current builds. Set up the connector on the web or desktop app instead — your account settings carry over.

The connection fails immediately. Confirm the URL ends in /mcp with no trailing slash: https://api.tempreon.com/functions/v1/tempreon-mcp/mcp.

Also connect: ChatGPT · Grok · Vibe (Le Chat)

Try saying...

"Start my session." — triggers session_start to load your Core Imprint
"Search my knowledge base for [topic] before you answer." — grounds the research in your Knowledge Vault
"Remember that [decision] — we chose it because [reason]." — stores an insight every connected model can use later