Skip to main content
Perplexity supports custom remote MCP connectors on paid plans, so you can connect TryPost and manage social media scheduling from Perplexity chat and Computer workflows.
This guide connects TryPost into Perplexity as a custom remote connector. Perplexity also ships its own search MCP for use inside other clients (Claude, Cursor, etc.) — that is a different product: Perplexity MCP Server.

​
Prerequisites

​
Setup

1

Open Connectors

In Perplexity, open Account Settings → Connectors. From Computer, you can also open Connectors in the left sidebar. Click + Custom connector.
2

Add a remote connector

Choose Remote and fill in:Acknowledge the risk notice for custom connectors, then click Add.
3

Authorize TryPost

Open the new connector card and complete OAuth. Sign in to TryPost, pick the Workspace this connection may use and click Authorize. To use another workspace, connect again and pick it. The connector should show as connected with TryPost tools available.
4

Use TryPost in a thread

Start a new conversation or Computer task, enable the TryPost connector for that thread if it is not already on, and ask:
Perplexity will call the TryPost tools to fetch your posts.
Perplexity reaches the MCP server from its cloud over HTTPS. The hosted endpoint https://app.trypost.it/mcp/trypost works out of the box. Self-hosted instances must be publicly reachable over HTTPS (or use a tunnel).
Choose OAuth 2.0 for the connector. TryPost rejects Personal Access Tokens on /mcp/trypost — an “API Key” auth mode in Perplexity will not work against TryPost MCP.
On Enterprise, admins can share connectors organization-wide and control whether members may add their own. Members still authenticate individually for OAuth connectors unless your admin configures organization-wide auth.

​
Example prompts