A Threads MCP server gives an AI agent tools for Threads, so a model can publish to your account instead of only drafting posts. Point Claude, Cursor, or any MCP client at Outstand's server and the agent can post text with optional media, chain a multi-post thread, repost, quote, reply to comments, and read views and engagement. Everything goes through Meta's official Threads API over an OAuth connection you approve once.
https://mcp.outstand.so/mcpclaude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any MCP client.
The server URL is https://mcp.outstand.so/mcp. Paste it into your client and connect Threads.
claude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
// claude_desktop_config.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}// .cursor/mcp.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}# Add a custom connector in your client's settings and paste # this URL, then sign in once in the browser. No API key to copy. https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any other MCP client. Full client setup guide.
The tools that apply to Threads, out of 27 on the server.
create_postPublish or schedule a Threads post, including a chained multi-post thread.repost_postRepost a published post, or quote it with your own commentary.create_replyReply to a comment on a post published through Outstand.get_repliesRead replies on a post published through Outstand.get_post_analyticsFetch views, likes, replies, reposts, and quotes for a published post.list_postsList posts, filterable by account, status, and date range.get_postFetch a single post and its per-platform publish status.delete_postDelete a post record in Outstand, cancelling it if it is still scheduled.upload_mediaStart a media upload and get a signed URL for an image or video.confirm_media_uploadConfirm an upload once the bytes are transferred and get the public URL to attach.list_social_accountsList connected social accounts, so the agent can find your Threads account.get_account_metricsFetch follower count and engagement for a connected Threads account.get_auth_urlGenerate an OAuth URL to connect a new Threads account.get_account_usageRead current billing-period post usage.No. Meta does not publish an MCP server for Threads.
Threads is also the thinnest ecosystem of any major network here. Where Instagram and X have dozens of community servers of varying quality, Threads has very few, and most of what exists is experimental. That cuts both ways: there is less to evaluate, and less risk of installing something abandoned, but there is also almost nothing to fall back on.
Outstand's is a hosted server on Meta's official Threads API. You connect with a normal OAuth consent screen, the server calls the documented publishing endpoints, and Threads gets the same tool surface as every other network you post to. If you are building agent workflows on Threads now, being early is most of the point.
Three realistic ways to give an agent Threads access, and what each one actually costs you.
| Approach | Setup time | Auth | Reliability | Compliance |
|---|---|---|---|---|
| Self-hosted open-source | Hours, and you are likely maintaining it yourself | Your own Meta app and Threads API tokens | Few maintained projects exist for Threads at all | Official API if it uses the Threads API rather than scraping |
| Directory-listed community server | Varies | Usually your own Meta app credentials | Very thin ecosystem. Most listings are experiments | Check the source before trusting it with an account |
| Hosted API-based (Outstand) | A few minutes: sign in, approve OAuth, paste the URL | Hosted OAuth link flow. Managed Keys included, no Meta app | Maintained against the official API, token refresh handled | Official Threads API. No scraping, no session cookies |
Connecting Threads is an OAuth link flow: Outstand opens Meta's consent screen, you approve, and the connection is done. There is no Meta developer app to register and no Threads API token to store yourself. Managed Keys are included on every plan and cover Threads.
Your agent can start this itself by calling get_auth_url and handing you the link. Bring your own OAuth app if you want your brand on the consent screen, but nothing about Threads requires it.
This is a publishing server, not a listening one. It does not scrape the Threads feed, pull follower lists, or monitor other accounts, and there is nothing ads-related in scope. Analytics cover the posts you published through Outstand: views, likes, replies, reposts, and quotes.
No. Meta has not shipped an MCP server for Threads, and the third-party ecosystem is very thin compared with Instagram or X. Most of what exists is experimental, which is why a maintained hosted server on the official API is worth more here than on a crowded platform.
Yes. Add https://mcp.outstand.so/mcp to Claude, connect your Threads account, and Claude can post, chain a thread, repost, quote, and reply. The same connector works in Cursor, Windsurf, ChatGPT, and any other MCP client.
Yes. Every action goes through Meta's Threads API over an OAuth connection you approved. Nothing is scraped and no session cookie is involved.
Yes, though media is optional on Threads rather than required. Upload an image or video, or pass a public URL, and the agent attaches it to the post. Text-only posts work fine too.
Yes. Give the agent the posts in order: the first publishes as the root post and the rest are chained as replies to it, which is how Threads models a thread natively. This is one of the few networks where chained multi-post publishing works end to end.
Yes. create_post takes a scheduled time, so an agent can queue a Threads post up to 30 days ahead. Scheduling runs in Outstand, and a scheduled post can be cancelled with delete_post before it goes out.
The MCP server is included with every Outstand account at no extra cost. Pricing is $19/month, 3,000 posts included, and posts published by an agent draw on the same quota as posts published through the REST API.
Every claim on this page is restated, dated, and citable on the facts page.
Sign in, approve Threads once, paste the server URL into your client. Then just ask your agent to post.
https://mcp.outstand.so/mcp