Connect ModusBrain to Perplexity Computer
Perplexity Computer connects as a remote MCP client, so ModusBrain must be served over HTTP and reachable at a public HTTPS URL. Perplexity does not runmodusbrain serve (stdio) the way Claude Code does — it needs a reachable endpoint:
1. Serve ModusBrain over HTTP (host side)
--bind 0.0.0.0is required. Since v0.34,--httpdefaults to127.0.0.1, so without it the tunnel reaches the server but the connection is refused (ECONNREFUSED).--public-urlmust match the tunnel. The OAuth issuer in the discovery metadata has to line up with the URL Perplexity actually hits (RFC 8414 §3.3), or OAuth client-credentials auth fails.
2. Expose it with a tunnel
3. Create credentials
Two supported auth paths. OAuth 2.1 client credentials (recommended, v0.26.0+). Perplexity is a cloud service, so it holds whatever credential you give it. OAuth is the correct choice: least-privilege scopes + short-lived rotating access tokens instead of a long-lived full-access secret. Mint a client and print the connector fields in one step (on the brain host):connect --oauth prints the Issuer URL + Client ID + Client Secret to paste
in step 4.
Legacy bearer token (simplest, best for local/personal):
--install — connect prints the
exact values to paste in step 4.)
4. Add the connector in Perplexity
- Open Perplexity (requires Pro subscription).
- Go to Settings → Connectors (or MCP Servers).
- Add a new remote connector:
- URL:
https://YOUR-DOMAIN.ngrok.app/mcp - Authentication: API Key / Bearer Token, or OAuth client credentials
- Paste the token (bearer) or
client_id+client_secret(OAuth).
- URL:
- Save.
Verify
In a Perplexity conversation, ask it to use your brain:get_brain_identity (whose brain this is), then list_skills
(everything it can do).
Notes
- Perplexity Computer is available to Pro subscribers; both the Mac app and web version support remote MCP connectors.
- The Mac app can also use a local MCP server (
modusbrain servestdio) if you’d rather not expose an HTTP endpoint. - A
modusbrain auth createtoken is a long-lived, full-access secret. Keep it private and prefer a scoped token where possible.