Connect / Perplexity
Connect Perplexity to Telara
Perplexity Enterprise can connect to Telara as a remote OAuth MCP connector. A customer administrator can share it across the organization, while each employee authorizes only their own governed Telara access.
The endpoint
Rolling it out centrally
Perplexity Enterprise administrators can share an approved remote connector across the organization and control whether members may add their own connectors.
Before you commit to this
Perplexity supports OAuth remote MCP connectors today. A curated permanent connector requires Perplexity partnership or directory review and must not be represented as approved until Perplexity confirms it.
Confirm it actually worked
The client's “connected” badge reports a successful handshake, not a tool call. Ask Perplexity something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=perplexity.
An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.
Support, privacy, and reviewer testing
The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.
For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.
Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.



