A private MCP connector for Threads data. Ask for a profile's posts, followers or following in plain English and the rows come back in the chat.
PostCopilot speaks the Model Context Protocol, so an AI client can call it directly. Claude can start a real export on our servers — no browser open on your machine — or read the exports your Chrome extension ran in your own logged-in session. Either way the rows land in a buffer only your connector can see, and Claude can filter, sort and summarise them without you touching a CSV.
Free: 3 server-side exports a day, up to 20 posts or 100 followers per export, plus 10 video downloads — the same allowance the free web tools give. No account, no email, no credit card. A $2 24-hour day pass or Queue Pro at $39.99/month lifts the server-side limits; they are the same plan, and only the duration differs.
They share one buffer and one set of reading tools, so once an export is in, it makes no difference which way it got there. They are priced differently, though, and for a reason worth knowing: the first one runs on our servers and is lifted by a website plan, the other two run in your browser and are lifted by the Chrome extension plan.
Ask for a profile and Claude calls export_posts, export_followers or export_following. The scrape runs on our servers — nothing has to be open on your machine, and you do not need a Threads login of your own.
A scrape takes roughly 20 seconds to 3 minutes. The tool waits inline for up to about 45 seconds, so most of the time the rows come straight back; if it is still going, Claude gets a job id and polls it with get_job. Nothing is lost either way — the finished export simply appears in the buffer.
Run an export the way you already do, in the PostCopilot Chrome extension, on your own logged-in Threads session. The file downloads to your Downloads folder exactly as before, and a copy lands in your buffer with a short handle like #A7F3.
This is the only path that reaches anything your login can see and a shared account cannot — and because that export ran in your browser rather than on our servers, it never counts against the free daily export allowance.
Ask for something only your own account can see — your home feed, a followers-only profile, your own search results — and Claude calls request_browser_export. The job waits in a queue until your Chrome is open with the extension running, then runs it on your session and drops the rows into the same buffer.
It is deferred, not instant, and the tool says so in every answer: there is no way to wake a closed browser. Claude tells you when your extension last checked in, so “queued” always comes with a reason. The file lands in your Downloads folder too, exactly as a hand-run export does.
Two families of tools: some run new exports, the rest read and manage what is already in the buffer. You never type a tool name — Claude picks them from what you ask for.
| Tool | What it does |
|---|---|
| Run a new export on our servers · lifted by a website plan | |
export_posts | Exports a profile's posts on our server and saves them to your buffer. |
export_followers | Exports the accounts that follow a profile — username, display name, follower count, verified status. |
export_following | The same, for the accounts a profile follows. |
download_video | Returns the direct, watermark-free media URLs for one post — every video with its width and height, and every photo. Takes a permalink or a /share/ link; share links are resolved to the real post first. |
get_job | Checks an export that was still running — server-side or browser — and returns the handle once it finishes. |
| Run an export in your own browser · lifted by the Chrome extension plan | |
request_browser_export | Queues an export for your own Chrome to run on your own Threads session — the only way to reach your home feed, a followers-only profile or your own search results. Deferred: it waits until your browser is open, and says so. |
| Read and manage the buffer | |
list_exports | Everything currently buffered: handle, kind, profile, item count, and when it expires. |
get_export | Reads one export's rows, paged — 50 at a time by default, 500 at most, so a big export never floods the chat. |
query_export | Filters and sorts without pulling everything: keyword, date range, minimum likes / replies / reposts, has-media; or minimum follower count and verified-only for people. Sort by newest, oldest, likes, replies, reposts or followers. |
delete_export | Deletes one export from the buffer. |
purge_buffer | Deletes everything in the buffer. Requires an explicit confirmation, so it cannot fire by accident. |
query_export call. The full list never enters the chat.The free PostCopilot Chrome extension. Nothing else to install, and no PostCopilot account to create.
Open the popup and switch on “Connect this extension to Claude”. It is off by default. A private connector URL appears with a Copy button.
Settings → Connectors → Add custom connector. Paste the URL. Claude discovers the tools by itself.
https://postcopilot.ai/mcp/connector/<your-token>
Treat that URL like a password. It is a bearer credential — anyone holding it can read your buffer, and nothing else. It can never reach another account's exports, and one click in the extension popup revokes it, which makes the old URL useless immediately. Clients that can send an Authorization: Bearer header should do that instead; the token-in-the-URL form exists because some connector UIs cannot set a header.
Prefer no extension? Sign in with Google here and create a connector straight from this page — same URL shape, same tools, nothing to install. That is also where you attach a $2 day pass or Queue Pro ($39.99/mo) if you want the server-side limits lifted.
The free connector gives exactly what postcopilot.ai's free tier gives — no more, no less. The row caps and the daily count are read from the same configuration the web tools use, so asking Claude is never the generous door and never the stingy one. The web tools and this connector move together.
| Free | Website plan | Extension plan | |
|---|---|---|---|
| Exports Claude runs on our servers | Free3 a day per device (5 a day per network) | Website plan10 an hour, no daily cap | Extension planSame as free — these run on our servers |
| Rows per export Claude runs | Free20 posts, or 100 followers or following | Website planUp to 2,000 items | Extension planSame as free |
| Video / photo downloads | Free10 a day (20 a network) — an abuse ceiling, not a paywall | Website planNo daily cap | Extension planSame as free |
| Reading server-scraped rows back | Free1 export a day; re-reads free | Website planUnlimited | Extension planSame as free |
| Exports queued to your own browser | Free10 a day, 1 waiting at a time | Website plan100 a day, 5 waiting | Extension plan100 a day, 5 waiting |
| Exports your extension uploads | FreeUp to 500 rows each, never counted against the daily number | Website planUp to 10,000 rows each | Extension planUp to 10,000 rows each |
| Held in the buffer | Free3 exports, for 6 hours | Website plan25 exports, for 24 hours | Extension plan25 exports, for 24 hours |
| Price | Free$0 — no account, no email | Website plan$2 for 24 hours, or $39.99/month | Extension plan$7.99/month |
The two paid plans are not two tiers of the same thing. They unlock different halves of the connector because those halves cost us wildly different amounts. When Claude runs export_posts, the scrape happens here: a browser process for 20 seconds to 3 minutes and a slot on the single shared Threads session every anonymous visitor borrows. That is a website resource, so a website plan lifts it. A browser export and a buffer upload cost us a database row, because the scraping happens in your Chrome on your own Threads session — so the Chrome extension plan lifts those. You never need both, and nothing is charged twice.
The $2 day pass and Queue Pro are the same plan. Same entitlement, same limits, same everything — the only difference is that one lasts 24 hours and the other renews monthly. Buying the pass again extends the window rather than restarting it.
Whichever you buy, nothing you have already set up changes. The connector URL already sitting in Claude keeps working — same URL, nothing to re-copy, nothing to reconnect, and the exports already in your buffer come with you. More about Queue Pro → · Compare the extension plans →
Server-side exports and video downloads are unlocked by a website plan — a $2 24-hour day pass or Queue Pro at $39.99/month, the same plan with a different clock. Because that plan lives on your PostCopilot account, the connector has to be attached to it once. Sign in and it takes one click.
Already have a connector from the extension? You do not need a new one. Sign in above and paste its token into Link an existing connector — the URL in Claude is untouched, and your plan applies within a minute. Linking binds a plan, not an identity: your buffer stays exactly where it is, and you can unlink at any time.
No Chrome extension at all? That works too. Sign in, press Create my connector, and paste the URL into Claude — no install, nothing to verify. You get the free allowance straight away, and whatever plan you hold applies to it.
If you just want to see what this feels like, PostCopilot has had a public MCP server since March. No token, no extension, no signup — add one URL to your MCP client and six tools appear: generate a Threads post, pull a video's download link, and export a profile's posts, followers or following.
https://postcopilot.ai/mcp
Transport is Streamable HTTP, and the server is stateless. Because it is anonymous and shares one Threads session with everyone using it, exports are capped at 2 per day per IP address, and results come straight back into the chat rather than into a buffer you own. That is the trade: zero friction, no privacy boundary, no filtering, nothing kept. The connector above is the same idea with your own private buffer around it. Full setup guide for Claude, Cursor and VS Code →
No. There is no signup, no email and no credit card. Install the free Chrome extension, tick “Connect this extension to Claude” in the popup, copy the connector URL it shows you and paste it into Claude as a custom connector. The extension mints an anonymous device-scoped token for you; nothing identifies you to us.
There are two reasons you might sign in anyway, and neither is required to get started: to create a connector with no Chrome extension at all, and to attach a $2 day pass or Queue Pro ($39.99/mo) so the server-side limits are lifted. A website plan is held on a PostCopilot account, which is why that one step needs a sign-in.
Any MCP client that can add a remote Streamable HTTP server. Claude's custom-connector UI is the one the setup instructions above are written for. The credential can travel either as an Authorization: Bearer header or inside the URL path, which is there for clients that cannot set a header.
3 server-side exports a day per device, and 5 a day shared across every free connector on the same network, resetting at midnight. Each one returns up to 20 posts, or up to 100 followers or following — exactly what a free export on postcopilot.ai returns, because both read the same configuration. Up to 3 exports are held at once, for 6 hours. Exports your own Chrome extension uploads do not count against the daily export number at all.
Video downloads are a separate counter — 10 a day per connector, 20 across a network. That one is an abuse ceiling rather than a paywall: postcopilot.ai/download does the same job free, with no account and no daily limit, so if Claude ever refuses a video it will point you there rather than at a plan.
Because handing rows to an agent is delivery. On the website a free user can run 3 exports and take 1 file away; the connector keeps the same shape, so the first read of each server-scraped export spends the daily allowance. Re-reading an export you already opened today is free and unlimited — every page of it, and every filter over it — so it is the second distinct export of the day that meets the wall, never the second call. Exports your Chrome extension uploaded are never metered, because they ran in your browser on your session and cost us nothing. Listing the buffer is free too, so you can always see what you have.
Yes — for the tools that run on our servers, that is exactly what unlocks them. Queue Pro at $39.99/month and the $2 24-hour day pass are the same plan with different durations, and either one lifts export_posts, export_followers, export_following and download_video: 10 exports an hour with no daily cap, up to 2,000 items each, unlimited video downloads and unlimited reads. Sign in with Google on this page and press Create my connector, or paste an existing token into Link an existing connector — the plan applies within a minute and the URL already in Claude keeps working.
The Chrome extension's separate $7.99/month plan is the browser-side one: it lifts the cloud buffer and the browser-run export queue. It does not lift the server-side tools.
Because they cost us wildly different amounts. When Claude runs export_posts, the scrape happens on our server: a browser process for 20 seconds to 3 minutes, plus a slot on the one shared Threads session every anonymous visitor borrows. That is a website resource, so a website plan unlocks it.
A browser export or a buffer upload costs us a database row, because the scraping happens in your Chrome on your own Threads session — exactly as it does when you click Export in the extension, which has never been metered. So the browser-side plan unlocks the browser-side things. You never need both, and nothing is charged twice.
6 hours on a free connector, 24 hours with any paid plan — the Chrome extension's $7.99/month plan or a website plan ($2 day pass / Queue Pro $39.99/mo) both extend it — after which they are deleted automatically. An expired export is never served, even if cleanup has not run. You can also delete one or wipe the whole buffer at any time by asking Claude, or with the “Delete my cloud buffer now” button in the extension popup.
Yes — treat it like a password. It is a bearer credential: anyone holding it can read that buffer. It only ever reaches one account's exports, it can never see another account's, and you can revoke it with one click in the extension popup, which makes the old URL useless immediately.
postcopilot.ai/mcp is the public, anonymous MCP endpoint that has been live since March. It needs no token and no install — you paste one URL and get five tools (generate a post, download a video, and export a profile's posts, followers or following), capped at 2 exports per day per IP, with results returned straight into the chat. The connector is the authenticated, per-user version: the same video download, plus a private buffer your exports live in, filtering and paging over those rows, exports queued to run in your own browser, and exports your Chrome extension pushed up from your own logged-in Threads session. Use the public endpoint to try it, the connector when you want it to be yours.
Yes, exactly as before. The connector is a side channel: the extension writes the JSON and CSV to your Downloads folder first, and only then sends a copy to your private buffer. The upload is never waited on and cannot fail an export. The setting also ships switched off — nothing leaves your browser until you turn it on.
Install the extension, tick one box, paste one URL — or sign in and create a connector here with nothing to install. Free either way: 3 server-side exports a day, up to 20 posts or 100 followers each, plus 10 video downloads — no account needed, no email, no credit card.
Want the server-side limits lifted? A $2 24-hour day pass or Queue Pro at $39.99/month does it — the same plan, and only the duration differs.
Download any profile's posts as CSV or JSON — free, no signup
Export followers and following lists from any Threads profile to CSV
Chrome extension to export followers & posts directly from Threads
Queue a list of @handles and get every profile's files by email