Publishing
Text ✅ · Images ⚠️ First only · Video ⚠️ First only
Inbox
Comments, Mentions, DMs
Analytics
Views, likes, replies, reposts
Why Postlaty
Why schedule Threads with Postlaty
Named AI models, then the composer
Generate the file with Veo, Nanobanana, Kling, Recraft, Grok, Flux, or Seedance, then schedule it to Threads from the same login. You are not exporting from another lab.
One clip, 19 networks
Cross-post the same encode to TikTok, Reels, Shorts, and the rest of Postlaty’s 19 channels. Each network keeps its own caption.
Inbox where the API allows it
Threads inbox: Comments, Mentions, DMs. Reply from Postlaty instead of hopping into the native app for every thread.
Cursor, Claude, ChatGPT via MCP
Connect Threads once. Then an agent on REST or MCP can generate and schedule to this account. Setup lives on each agent page (for example /cursor).
MCP
Ask Cursor, Claude, or ChatGPT
Connect Threads in Postlaty, add MCP, then paste this.
Generate a post for Threads and schedule it tomorrow at 9:00. Use my connected Threads account in Postlaty.
Setup for each client: all agents · API docs
FAQ
Frequently Asked Questions
Sign up, connect Threads (OAuth Allow popup), then create in the AI tab or upload a file and schedule from the composer. Starter is $29/month for 10 channels across 19 networks, with a 7-day trial.
You connect Threads through Meta OAuth (an Allow popup), which is the same family as Instagram but its own connection. Posts take the first image or video only. Replies, mentions, and DMs are in Inbox.
Yes. Create an API key in Profile, add the Postlaty MCP server to the agent, connect Threads in the app, then ask it to generate and schedule. Same pipeline as the UI.
No. Threads is one of 19 networks. The same subscription includes the AI studio, inbox where supported, REST, and MCP.
