Threads API MCP server

MCP server · 6 tools · 5 endpoints

Threads MCP server

Profiles, post timelines, post stats and keyword search from public Threads, for an agent that knows the platform publishes no view counts.

100 credits on signup · No card · Sign in with OAuth or paste a key

scrapersocial-threads mcp.scrapersocial.com/threadsconnected
you

Who is <@handle> on Threads? I want the bio and how many followers they have.

agent
calls get_profile 4 credits / profile
{ "handle": "<handle>" }
server
returns
followers number subscribers number bio string
Shape only. Keys follow the tool's summary; a real call returns the full record. 1 call · 4 credits

Connect

One URL. Your client already knows what to do with it.

The first call opens a sign-in. New accounts get 100 credits, no card. Every client below shares one account and one balance.

Get a free key
server url https://mcp.scrapersocial.com/threads
claude.aiOAuth

Settings → Connectors → Add custom connector, then paste the server URL.

mcp.scrapersocial.com/threads

Web, desktop and mobile. Nothing else to paste.

Claude Codeone command

Run this in a terminal.

$ claude mcp add --transport http scrapersocial-threads https://mcp.scrapersocial.com/threads

Approve the sign-in prompt on first use.

Cursorone click

Installs the server and opens the MCP panel.

Add to Cursor
or paste the JSON into .cursor/mcp.json
{ "mcpServers": { "scrapersocial-threads": { "url": "https://mcp.scrapersocial.com/threads", "headers": { "Authorization": "Bearer sk_live_..." } } } }
Other clients · VS Code, Windsurf, Gemini CLI, anything that speaks MCP
VS Codeone click or JSON
Add to VS Codeor run MCP: Add Server, choose HTTP and use:
{ "name": "scrapersocial-threads", "type": "http", "url": "https://mcp.scrapersocial.com/threads" }
Windsurf~/.codeium/windsurf/mcp_config.json
{ "mcpServers": { "scrapersocial-threads": { "serverUrl": "https://mcp.scrapersocial.com/threads", "headers": { "Authorization": "Bearer sk_live_..." } } } }
Gemini CLI~/.gemini/settings.json
{ "mcpServers": { "scrapersocial-threads": { "httpUrl": "https://mcp.scrapersocial.com/threads", "headers": { "Authorization": "Bearer sk_live_..." } } } }
Any clientStreamable HTTP · OAuth 2.1 or Bearer
$ npx add-mcp https://mcp.scrapersocial.com/threads

One account and one balance across every client and the every-platform hub at mcp.scrapersocial.com.

What it does

What your agent can do with Threads

Threads doesn’t publish view counts, so no tool here will return one. What it does publish, and what this server reads, is a profile with follower count and bio, an account’s posts with likes and reply counts, stats for a single post, and keyword search across public posts. Five endpoints, four of them wired to named tools.

get_profile costs 4 credits per handle. get_channel_posts lists an account’s recent posts for 3 each. get_post_stats takes a post URL and returns its engagement for 3. search matches a keyword against public posts for 4 per result. The fifth endpoint, user-search, finds accounts by name for 4 per result and is reachable with call_endpoint; list_endpoints lists it alongside the others for free.

Threads is young and tooling for it is thin, which is the main reason to bother: a JSON read that works is worth more on a network few tools cover. The server fits an agent that tracks what a handful of accounts post, watches for a brand or keyword, or compares a creator’s Threads presence with their Instagram one. It’s also the narrowest of the Meta platforms here, with no comments, transcript or download capability, so don’t promise a reply tree your agent can’t fetch. Engagement fields are what Threads shows publicly, nothing estimated.

Four jobs it finishes on its own

01

Follow a set of accounts without the app

Point get_channel_posts at each handle you care about and the agent hands you the new posts with their like counts. Three credits a post, no feed algorithm in the way.

02

Track a keyword as the network grows

search at 4 credits per result returns public posts matching a query. Run it daily and you'll see when a topic starts to move on Threads before it's obvious elsewhere.

03

Compare Threads and Instagram for one creator

Call get_profile here and the same tool on the Instagram spoke. The agent can then tell you whether a creator's audience followed them across or stayed put.

04

Check a single post's numbers

get_post_stats on a post URL returns likes, replies and reposts where Threads publishes them. Three credits, one JSON object, no screenshots.

Limits · read before you connect

What this does not do

Written by a person, not generated. If something here is wrong, tell us.

Public Threads only. A private profile reads as not found, at zero credits. Views aren’t a public metric on Threads, so they’re absent from every response rather than estimated. There’s no comments tool, no replies endpoint, no transcript, summary or download; the catalog has five paths and that’s the lot. Post listings and search return up to 50 items per page at 3 or 4 credits per item, with a minimum of 1 credit on any successful call. The server reads; it doesn’t post or reply.

Tools

6 tools, same names as the every-platform hub

Four do one Threads thing each. The last two reach all 5 endpoints by path, so nothing in the catalog is out of an agent's reach.

Full credit table →

Get post engagement stats

get_post_stats

Engagement stats for one public post or video: views, likes, comments, shares and reposts where the platform publishes them.

3 credits / post

Get an account profile

get_profile

Profile, page or channel record for a public account: follower and subscriber counts, bio, and totals.

4 credits / profile

List an account's posts

get_channel_posts

Recent public posts or videos from one account, with per-item metrics.

3 credits / post

Search a platform

search

Keyword search over one platform's public content.

4 credits / result
Reaches the other 1 endpoint

List every Threads endpoint

list_endpoints

Browse every Threads endpoint, its input and its credit cost. Free, and calls nothing upstream.

free

Call any Threads endpoint by path

call_endpoint

Run any Threads endpoint by its path, so nothing Threads offers is out of reach of an agent.

endpoint's own cost

Pricing

100 free credits is 33 stats lookups, or 25 profile reads.

Then $5 a month for 1,000 credits, or $4 per 1,000 as a top-up. No card to start. Calls cost between 3 and 4 credits on Threads.

33 stats lookupsget_post_stats · 3 each
25 profile readsget_profile · 4 each
Get a free key 100 credits on signup · $5 for 1,000 · full credit table

Prompts

Things to ask once it is connected

Copy one, swap the placeholder, paste it into your client.

Who is <@handle> on Threads? I want the bio and how many followers they have.

Show the 20 newest posts by <@handle> with like and reply counts.

What are the stats on <threads-post-url>?

Search Threads for "<keyword>" and show me the 15 most-liked results.

Find Threads accounts named <name> and tell me which one is the real one.

Compare <@handle> on Threads with the same handle on Instagram: followers and posting frequency.

Questions

Before you connect

Do I need a Threads or Instagram login? #

No. Authentication is your ScraperSocial key. The server reads Threads as a logged-out visitor.

Why are there no view counts? #

Threads doesn't publish them. The server returns the metrics the platform shows, likes and reply counts among them, and leaves views out rather than inventing a number.

Is this Meta's Threads API? #

No, Meta has nothing to do with it. ScraperSocial is independent and unaffiliated with Meta, Instagram or Threads. Meta's own Threads API is for publishing from accounts you own.

Can I read the replies to a post? #

No. Threads has no comments or replies endpoint in this catalog. get_post_stats tells you how many replies a post has, not what they say.

What does a search cost? #

Four credits per result, so ten results run 40 and a maximum page of 50 runs 200.

Can it read a private profile? #

No. A private account yields not found, and no credits move.