[integrations] Perplexity Pro MCP compatibility

[demarant]

Contribution Type

• Recipe (/recipes)
• Schema (/schemas)
• Dashboard (/dashboards)
• Integration (/integrations)
• Skill (/skills)
• Repo improvement (docs, CI, templates)

What does this do?

Adds integration documentation for connecting Perplexity Pro as an MCP client to Open Brain. Provides step-by-step instructions for configuring the Bearer auth connection (introduced in the companion server PR), enabling Perplexity to search and capture thoughts directly. The four MCP tools (search_thoughts, list_thoughts, thought_stats, capture_thought) become available in Perplexity.

See screenshot below from Perplexity chat:

Documents integration for:
#73

Requirements

• Working Open Brain setup with updated MCP server (Bearer auth support — see PR [server] Add Authorization Bearer support for MCP clients #154)
• Perplexity Pro subscription
• No additional tools or services required

Checklist

• I've read CONTRIBUTING.md
• My contribution has a README.md with prerequisites, step-by-step instructions, and expected outcome
• My metadata.json has all required fields
• If my contribution depends on a skill or primitive, I declared it in metadata.json and linked it in the README — N/A (no dependencies)
• I tested this on my own Open Brain instance — Tested on Perplexity web and mobile app; verified both retrieval and storage of thoughts
• No credentials, API keys, or secrets are included

[justfinethanku]

Thanks for putting this together. I’m not merging it as-is, but there’s real potential here.

What needs to change:

• split the integration/docs work from the unrelated fingerprint backfill changes
• make the backfill pagination deterministic if that cursor rewrite is going to live anywhere, for example with a composite cursor like created_at + id
• make the Bearer-auth prerequisite explicit so the integration boundary is clear

There’s a useful PR in here, but it needs to become a focused, self-contained contribution before we can merge it.

[justfinethanku]

Thanks for putting this together. I’m closing this PR in its current form because it no longer has a clean merge path.

Right now it depends on the core Bearer-auth change from #154, and that companion PR has been closed as out of scope for community contributions. This PR also bundles unrelated backfill and server/template changes, so even apart from the dependency it still isn’t a mergeable unit.

If the Perplexity integration is still something you want to pursue later, the best path is a fresh, narrower PR that only covers the integration once the underlying auth story exists in an approved form.