Threads Scraper

com.quarralabsPublished by quarralabs.comv1.0.0Updated Nov 4, 2026

Threads public posts, replies and profiles, with view counts, keyword and account search.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Apify-hosted MCP server that lets an assistant collect public Threads posts, replies and profiles, including view counts and keyword or account search.

What you can do
  • Collect public Threads posts and replies, with view counts.
  • Look up public Threads profiles.
  • Search Threads by keyword or by account.
  • Runs as a hosted Apify Actor exposed over a remote MCP endpoint.
When to use it
Useful when you want an assistant to gather public Threads content for research, social listening, or tracking what accounts and keywords are posting, without building your own scraper.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or an empty header to sign in to Apify with OAuth. An Apify account and network access are needed.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret and prefer OAuth sign-in where possible. Apify usage is typically billed per run or per result, so scraping volume can cost money. Collected data is public Threads content sent to Apify and returned to the assistant; respect Threads terms and applicable privacy rules.

Installation

In SourceWeft

  1. Open Threads Scraper in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.quarralabs%2Fthreads-scraper/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "threads-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=quarra/threads-scraper"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.