Perplexity's custom remote connectors — launched March 13, 2026 — let you wire any MCP-compatible service into your search-and-answer experience. Once Truthifi is added, every Perplexity thread can pull live, read-only data from your real financial accounts. Ask "what's my actual cash drag across all accounts?" and Perplexity returns numbers, not generic advice — combined with its usual web-search context layer.

This guide walks the full setup. It takes about two minutes assuming you already have a Truthifi account.

Before you start

You'll need:

• A Perplexity Pro, Max, or Enterprise plan. Free Perplexity does not support custom connectors — the feature requires an active paid subscription, since the underlying compute and storage are non-trivial for Perplexity to provide.

• A Truthifi account with at least one financial institution already linked. New to Truthifi Connect?

• Your Truthifi MCP endpoint, which is the same for every user: https://api.truthifi.com/mcp.

• About two minutes.

You don't need an API key, a developer account, or any special access at Perplexity. The connector flow is fully self-service from your account settings.

Step 1 — Add Truthifi as a custom connector

In Perplexity:

1. Open Account Settings → Connectors. Click + Custom connector in the top-right.

2. In the modal that appears, choose Remote.

3. Fill in the connector details:

• Name: Truthifi

• MCP Server URL: https://api.truthifi.com/mcp

• Description: Read-only access to your real portfolio data via Truthifi

• Authentication: OAuth 2.0

• Transport: leave at the default — Perplexity auto-detects Streamable HTTP, which is what you want

• Icon (optional): Truthifi mark, max 128 KB

1. Check the risk-acknowledgement box (Perplexity requires this for any custom connector).

2. Click Add. Truthifi appears in your Connectors screen.

That's the full add flow. Setup-side, you're done.

A note on the risk-acknowledgement step: Perplexity applies this checkbox to every custom connector regardless of provider. The acknowledgement reflects that you're authorizing data flow from an external service. For Truthifi specifically, the data flow is read-only — Perplexity reads portfolio facts; nothing is written back, no transactions are placed. The checkbox is required by Perplexity's policy, not by any Truthifi-specific risk.

Step 2 — Activate Truthifi in a conversation

Click the Truthifi connector card on your Connectors screen to start the OAuth flow. Perplexity redirects you to Truthifi to sign in. Authenticate with your existing Truthifi credentials, review the requested scope (read-only access to portfolio data, balances, holdings, and Truthifi Score), and click Allow. Perplexity returns you to your Connectors screen with Truthifi enabled.

To use Truthifi in a thread, start a new conversation and toggle Truthifi on from the connector picker. Perplexity will pull from Truthifi alongside its standard web-search layer when answering questions that involve your portfolio.

If you forget to toggle Truthifi on at the start of a thread, Perplexity will give you a generic answer and may suggest you enable a relevant connector. You can toggle Truthifi on mid-thread; Perplexity will retrieve the data on the next turn.

Step 3 — Test the connection

Start a new thread and ask something specific to your accounts:

• "Use Truthifi to show my current asset allocation."

• "What's my cash drag across all accounts?"

• "Pull my top five positions by current value."

Perplexity should respond with your actual numbers, citing Truthifi as the source. If you get a generic "I don't have access to your accounts" answer, the connector wasn't toggled on for the thread — check the connector picker at the start of the conversation.

The first time you ask a portfolio question, Perplexity may take a few seconds longer than usual as it negotiates with the MCP server and discovers the available tools. Subsequent calls in the same thread are fast. When Perplexity does call Truthifi, the response includes Truthifi-tagged citations distinct from web-source citations — you can verify exactly which numbers in the answer came from your accounts versus from Perplexity's standard web search.

Why Truthifi — and not just any data source

You can paste a CSV into Perplexity. You can describe your portfolio in plain English. You can ask Perplexity to "assume I have $100k spread across these accounts" and run hypotheticals. None of these grounds Perplexity in your real situation.

Truthifi connects to your real financial institutions — brokerages, banks, retirement accounts, crypto exchanges — through industry-standard aggregation, normalizes the data into a consistent schema, and exposes it via MCP. Your brokerage credentials stay at your brokerage. Perplexity gets a scoped, read-only OAuth token. When data changes, Truthifi reflects it the next time Perplexity queries.

The MCP layer matters specifically because Perplexity is search-augmented. When you ask "should I rebalance toward more bonds given current Treasury yields," Perplexity combines its web-search layer (current Treasury yields, market commentary) with Truthifi's data layer (your actual current allocation). The answer is grounded in both general knowledge and your specific situation — exactly what you'd want from an AI agent helping you think through portfolio decisions. And because Perplexity's signature is citation-rich answers, you can verify both layers — the public-context citations point to specific market sources, and the Truthifi citations point to specific account data.

What to ask once you're connected

Perplexity with Truthifi shines on questions that combine portfolio facts with web context. Some places to start:

• Allocation reality: "Compare my actual allocation to a 70/25/5 target. What would I need to do to rebalance?"

• Web-augmented fee benchmarks: "Pull my fund expense ratios and tell me whether they're competitive given current market alternatives."

• Tax-context decisions: "Which positions should I consider tax-loss harvesting before year-end? Factor in current wash-sale rules."

• Drift-driven reallocation: "Which of my positions has drifted most from my target allocation in the past quarter?"

• Cross-account totals: "Total my retirement accounts across all custodians and tell me how that compares to typical balances at my age."

Perplexity calls Truthifi mid-thread — no need to pre-load context. Ask, get answer, follow up.

Perplexity mobile and desktop

The Truthifi connector works the same way across Perplexity's web app, iOS, Android, and macOS clients. Set it up once in account settings; it's available everywhere you sign in. The OAuth tokens stay scoped to your Perplexity account, not your device.

If you're using the Perplexity desktop app and the OAuth flow doesn't return cleanly to the app, that's typically a system browser issue — manually return to Perplexity desktop after completing OAuth in your default browser.

Team and Enterprise plans

Perplexity Enterprise admins can publish Truthifi as an organization-wide connector. The flow is similar to the individual setup but happens at the workspace level: admin adds Truthifi from the Connectors screen with the same URL and OAuth, then publishes to specific user groups or the whole organization.

End-users on the workspace then see Truthifi pre-listed in their personal Connectors. They click to connect and run their own OAuth flow — admin publishing only sets up the connector definition, not the per-user token.

This pattern is useful for advisors who want their team using a shared Truthifi-MCP setup, with each advisor authenticating to their own client portfolio (or however your firm scopes it).

To revoke access

You can disconnect from either side:

• From Perplexity: Account Settings → Connectors → Truthifi → Remove. Perplexity discards the connector definition and the stored OAuth token.

• From Truthifi: truthifi.com → Settings → Connected Apps → Perplexity → Revoke. The next Perplexity call to Truthifi fails authentication and Perplexity reports the disconnection.

Revoking from Truthifi is the more thorough option if you're concerned the Perplexity-side state has gotten stale. Revoking from Perplexity is cleaner if you're just removing the connector and might re-add it later.