Let your AI agent post to Threads

Can an AI agent post to Threads?

Postgale is the secure layer for AI agents on social media. This page covers Threads: what an agent can publish and answer, what you need, the rules Postgale applies, and how to connect.

Threads posts are created as containers and published in a second step, and a long thread is a chain of replies to your own post. Postgale hides that: the agent sends the text (and optional media or a list of thread items) and gets back one post with its permalink.

MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude and Cursor use outside tools. An MCP server is what they connect to. Postgale hosts one and a REST API, so ChatGPT, Claude, Cursor, VS Code, n8n or your own agent can use Threads as a tool.

What do you need?

• A Threads account; the owner signs in once with Threads.
• A Postgale workspace, and a sign-in or an API key for the agent.
• For image, video or carousel posts: media on a public HTTPS URL.
• An AI tool that can call Postgale: ChatGPT, Claude, Cursor, n8n, VS Code, or your own code.

What can the agent do on Threads?

Which Threads rules does Postgale enforce?

• Text up to 500 characters per post. Longer content goes in a reply chain, not a cut-off post.
• Carousels take 2 to 20 items. Media comes from a public HTTPS URL and is processed by Meta before Postgale publishes.
• Threads limits posts and replies per 24 hours (250 posts and 1,000 replies by default). Postgale reads the live quota before publishing.
• Tokens last 60 days and are refreshed by Postgale before they lapse.

How do I connect Threads to an AI agent with Postgale?

1. Create a Postgale workspace and open Dashboard → Accounts.
2. Choose Connect Threads and sign in with the account you own. Postgale stores the tokens, encrypted, and refreshes them for you.
3. Connect your AI tool: add https://postgale.com/mcp in ChatGPT, Claude or Cursor and sign in to Postgale, or create a key under Dashboard → API keys for n8n or your own code.
4. Ask the agent for a draft first. Turn on approval in the dashboard if a person should sign off before anything goes live.

An agent can also start the connection itself: the connect_account tool (or GET /api/v1/connect/threads) returns a sign-in link that is valid for 10 minutes and that the account owner opens in a browser. The agent never sees the password or the tokens.

What does a Threads post from an agent look like?

Ask your agent“Turn the launch notes into a 4-post thread for Threads, tag it under “fall”, allow replies from followers only, and schedule it for Thursday 9am Eastern.”

{
  "content": "The fall drop is live. Shipping Thursday.",
  "scheduledFor": "2026-10-22T13:00:00Z",
  "platforms": [
    {
      "accountId": "acc_threads",
      "platformSpecificData": {
        "topicTag": "fall",
        "replyControl": "accounts_you_follow",
        "threadItems": [
          {
            "content": "The fall drop is live. Shipping Thursday."
          },
          {
            "content": "Three fabrics, one cut."
          },
          {
            "content": "Sizes XS–XXL, restock in November."
          }
        ]
      }
    }
  ]
}

Nothing has to go out unreviewed. Approval can be required per workspace, per connected account, per API key or per signed-in app; while it applies, posts wait as pending approval in the dashboard, and replies, direct messages and edits to live posts are refused. Every write the agent makes is kept in the audit log.

What can’t an agent do on Threads through Postgale?

• Send direct messages. Threads has no messaging API.
• Edit a published post. Threads allows delete, not edit.

Common questions