Developer Guide

Post to X from Perplexity Computer
Comet Drafts. Computer Publishes.

Yes, Perplexity Computer can post to X. Add one custom remote MCP connector pointed at mcp.opentweet.io/mcp and Computer publishes, threads, and schedules on your connected account.

The qualifier: custom connectors need a paid Perplexity plan. They shipped on Pro, Max, and Enterprise on March 13, 2026, and there is no custom connector option on Free.

Last updated: September 2026

7-day free trial. Cancel anytime.

Comet and Computer are two different products

Most guides blur these together and then hand you steps that do not exist in the product you opened. Comet is the browser. Computer is the agent. Only one of them is a sensible place to publish from.

Factor	Perplexity Comet	Perplexity Computer
What it is	A Chromium browser with an assistant in the sidebar	An agent platform that runs long, multi step tasks
Launched	Went free on March 23, 2026	February 25, 2026 on Max, Pro on March 13, 2026
Reads the live web	Yes, that is the whole point	Yes, plus files and connected apps
Custom MCP connectors	Connectors are a Perplexity account setting, not a Comet feature	Yes, enabled per task from your account connectors
Publishes to X	Only by clicking around a logged in tab	Yes, through a connector, with a post id returned
Schedules a post for later	No	Yes, via the scheduling tools on the connector

Why the connector beats the browser click

Comet can drive a logged in X tab, and it is tempting to let it press Post. It gives you no post id, no scheduling, no retry, and a silent failure reads exactly like a success. A connector call returns a result you can log and act on. The longer version of that argument is on Can Perplexity post to X.

What you need

A paid Perplexity plan

Pro at $20 a month, Max at $200 a month, or an Enterprise seat. Computer runs on all three. Max buys more credits and higher spend limits, not a different connector feature.

An ot_ API key

Created at /developer. It is the only credential the connector holds.

A connected X account

Connected once inside OpenTweet. No X developer app, no OAuth to maintain, no per post metering.

Step-by-step: connect OpenTweet to Perplexity Computer

Get your OpenTweet API key

Create an ot_ key at /developer and connect the X account you want Computer to publish to. Copy the key now, because OpenTweet shows it once.

Add the remote connector

In Perplexity, click your profile in the lower left, open All settings, then Connectors. Click + Custom connector and choose Remote. Fill in these values.

perplexity custom connector

Name:            OpenTweet
MCP server URL:  https://mcp.opentweet.io/mcp
Transport:       Streamable HTTP
Authentication:  API key
Key value:       ot_your_key

Tick the box acknowledging that custom connectors can introduce risk, then click Add. The URL must be HTTPS. The OpenTweet server only accepts an Authorization: Bearer ot_ header, so choose the API key option rather than OAuth.

What we could not confirm from a primary source

Perplexity's own help centre pages block automated fetches, so the field labels above come from third party setup guides published in 2026 and from Perplexity's March 13, 2026 changelog, which confirms the feature, the plans, and the OAuth, API key, or none choice. We could not independently confirm the exact header Perplexity sends when you pick API key. If the connector fails to authenticate, that is the field to look at first, and the fallback below works regardless.

Verify the tools appear

Open a Computer task, make sure the OpenTweet connector is enabled for it, and ask something read only first. A read that succeeds proves both the transport and the key.

first prompt

List my scheduled OpenTweet posts for the next 7 days.

A returned queue means all 43 OpenTweet tools are reachable. The full list is in the MCP docs, and the posting tools specifically are covered on Post to X over MCP.

Research, draft, and schedule in one task

This is what Computer is actually for. A single instruction can span research, drafting, timing, and publishing, and it keeps running while you close the tab.

computer task

Research what changed in X API pricing this quarter.
Draft a 4 post thread with one cited number per post.
Check my best posting time, then schedule the thread
for the next available slot. Do not publish immediately.

Computer does the research with its own models and calls the OpenTweet tools only for the parts that touch your account: checking best times, creating the thread, and scheduling it.

Keep a human in the loop

Computer is built to run unattended, which is exactly why the publishing step should not be immediate. Tell it to schedule rather than publish, and posts land in your OpenTweet queue where you can still edit or cancel them.

standing instruction

Always set scheduled_date. Never use publish_now.

If you would rather the decision live in your own code than in the model, call POST /api/v1/posts directly and let Computer hand you the text. Both routes use the same key.

Fallback: run the server locally on macOS

Use this if the remote connector is unavailable on your account or your organisation blocks third party remote servers. As of July 2026 local MCP connectors in Perplexity are macOS only.

Install the PerplexityXPC helper application, which is what lets Perplexity launch and talk to a local MCP server. Then go back to Connectors, click Add Connector, choose the Simple tab, and give it a name and a launch command. Save, wait for the connector to report Running, then enable it under Sources.

local server command

npx -y @opentweet/mcp-server

# with the key in the environment
OPENTWEET_API_KEY=ot_your_key npx -y @opentweet/mcp-server

The local server exposes the same tools as the hosted one. Client by client setup for every other MCP host is on the MCP server page, and the shorter Perplexity overview is on the Perplexity integration page.

What it costs

You are already paying Perplexity. The only question is what the posting layer adds, and whether it meters you per post.

Factor	Computer + OpenTweet	Computer + X API directly
Perplexity	Pro $20/mo or Max $200/mo, Computer included on both	Same, this cost does not change
Posting layer	OpenTweet Pro, flat $11.99/mo	X API, pay per use
Per post fee	$0	About $0.015, about $0.20 with a link
X developer account	Not needed	Required, with billing enrolled
Auth you maintain	One ot_ key in the connector	OAuth2 user token you refresh
Scheduling	Included	Not offered by the X API

The maths for a Max subscriber

At $200 a month for Perplexity Max, an $11.99 flat posting layer is a rounding error, and it removes the one thing the X API meter punishes hardest: posts containing links, at about $0.20 each. Full plan detail is on pricing.

Common issues

There is no custom connector button

You are on Free. Custom connectors require Pro, Max, or Enterprise. On Enterprise the button can also be hidden until an administrator enables member added custom connectors in the enterprise connector settings.

The connector adds but Computer never calls it

Connectors live at the account level and are enabled per task. Open the task, confirm OpenTweet is switched on for it, and name the tool explicitly in your prompt the first time, for example asking it to use the OpenTweet connector to schedule the post.

Tools are discovered but nothing publishes

Almost always no connected X account on the OpenTweet side. Discovery only proves the transport works. Open your OpenTweet dashboard, connect X, then retry. If you run several X accounts, pass the account id so the agent does not guess.

401 Missing or invalid Authorization header

The server received no usable bearer token. Check the key still starts with ot_, has not been revoked, and was pasted without a trailing space. If the API key auth type in Perplexity does not produce a working header on your build, use the local server fallback, which reads the key from the environment instead.

You are in Comet and cannot find any of this

Connectors are a Perplexity account setting rather than a Comet browser feature, and the publishing surface is Computer. If you want the broader picture of which agents can publish and which can only draft, see which AI agents can post to X in 2026.

Frequently asked questions

Can Perplexity post to X?

Not on its own, but Perplexity Computer can once you give it a posting tool. Perplexity has no connection to your X account and no publishing capability of its own. Add the OpenTweet MCP server as a custom remote connector at https://mcp.opentweet.io/mcp and Computer gains tools to publish, thread, and schedule on your connected account.

How do I add a custom MCP server to Perplexity Computer?

Open your profile in the lower left of Perplexity, then All settings, then Connectors. Click + Custom connector and pick Remote. Enter a name, the HTTPS MCP server URL, pick Streamable HTTP as the transport, choose an authentication type of OAuth, API key, or none, tick the box acknowledging that custom connectors carry risk, and click Add. The connector is then available to enable inside a Computer task. Custom connectors shipped on March 13, 2026 and require a paid plan.

What is the difference between Perplexity Comet and Perplexity Computer?

Comet is the Chromium based browser with an assistant that reads the page you are on and can drive tabs. It went free on March 23, 2026. Computer is the agent platform that runs long, multi step tasks across models and connectors. Computer launched February 25, 2026 for Max subscribers and opened to Pro subscribers on March 13, 2026. For publishing to X, Computer is the surface you want, because a connector call returns a post id while a browser click does not.

Which Perplexity plan do I need to add a custom MCP connector?

A paid one. Custom connectors are available on Pro at $20 a month, Max at $200 a month, and Enterprise. Free accounts have no custom connector option at all, which is the single most common reason this setup stalls. On Enterprise, an administrator may also need to enable member added custom connectors before the button appears.

Do I need an X developer account for Perplexity Computer to post?

No. OpenTweet holds the X connection, so Computer only ever calls OpenTweet with your ot_ key. Calling the X API directly instead would mean creating an X developer app, handling OAuth refresh, and paying per use at about $0.015 per post or about $0.20 per post if the post contains a link.

Can Comet just click the post button on X for me?

It can operate a logged in X tab the way a person would, but it is a poor publishing foundation. It breaks when the interface changes, it cannot schedule or retry sensibly, and a failed post looks the same as a successful one because nothing is returned. A connector call gives you a post id and a status you can act on.

Keep exploring

OpenTweet vs the X API

Post, schedule, and automate X without a developer account or the $200/mo minimum.

X DM outreach, human-approved

Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.

Post to X without an API

The clean, account-safe way to post to X from your code or an AI agent.

Twitter MCP Server

Give Claude, Cursor, and OpenClaw the ability to post to X. 43 tools included.

Developer docs

Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.

Cross-posting reference

One call posts to X and mirrors it to Bluesky. The platforms field, per-network results, and why a network gets skipped.

XMCP vs OpenTweet

X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.

MCP for AI agents

Connect your AI client to X in under two minutes, no X developer account.

Developer API and keys

REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.

OpenTweet for AI agents

The posting layer for autonomous agents and automations that live on X.

Build an AI Twitter persona

Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.

Best MCP servers for social media

The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.

Cheapest way to post to X via code

Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~60 posts a month.

Let Perplexity Computer publish what it researches

One connector URL, one ot_ key, and the research your agent already does ends on your timeline instead of in a chat log. Flat $11.99 a month, no X developer app.