Mcp Threads Keyword Search

com.mambabuiltPublished by mambabuilt.comv1.0.1Updated Nov 7, 2026

Threads posts by keyword with exact phrase matching, author, date, likes, and link, no login

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Searches public Threads posts by keyword through an Apify actor and returns one row per matching post with text, author, date, likes, replies, reposts and link.

What you can do
  • Search Threads posts by keyword and get one flat row per post with text, author, publish date, likes, replies, reposts, quotes and post link
  • Filter results by age, minimum likes, whether replies are included, and match mode (exact phrase, all words, or off)
  • Cap posts per keyword, deduplicate posts matched by several keywords, and skip posts already returned by earlier runs via a named memory key
  • Receive one free summary row per keyword
When to use it
Useful for social listening and research on public Threads conversations: finding recent posts about a topic, a competitor or a product category, and collecting engagement counts for analysis. It suits scheduled keyword monitoring rather than account management, since it needs no Threads login.
Requirements
Runs locally as an npm package via npx, so Node.js 18 or newer is needed. Requires an Apify account and an Apify API token supplied as the APIFY_TOKEN environment variable; the tool is listed without a token but calls fail without one. Network access to Apify is required.
Before you install
Calls are billed per event to your Apify account (per returned post row plus a per-run start fee), so searches cost money; an optional max_charge_usd cap can limit a run. The APIFY_TOKEN is a billable credential and should be kept out of shared configs. Search results are public posts sent to Apify for processing.

Installation

In SourceWeft

  1. Open Mcp Threads Keyword Search in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Threads Keyword Search MCP Server

[npm version] [license]

An MCP server for the Mamba Labs Threads Posts by Keyword, Exact Match actor on Apify. Search Threads for keywords and get one flat row per post that contains them.

What's Inside

What it does

Each keyword is searched the way Threads search works for a visitor who is not logged in, which shows about 20 to 25 posts per search. By default a post is kept only when the keyword's words are in its text, next to each other and in order, so loosely related results are set aside and not charged. A post found by several keywords is returned once with every keyword it matched. Filters for age, likes, and replies, and an only new posts memory for schedules. Each keyword also returns one free summary row. No Threads or Instagram account, login, or key is used.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-threads-keyword-search": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-threads-keyword-search"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The search_threads_posts tool appears.

Prerequisites

Example prompts

  • "Find Threads posts about cold email from the last 30 days."
  • "Which Threads posts mention our competitor by name this week?"
  • "Collect Threads posts about hubspot alternatives with their like counts."

Tool

search_threads_posts. One tool. Example arguments:

json
{  "keywords": [    "cold email",    "hubspot alternative"  ],  "match_mode": "phrase",  "since_days": 30}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
keywordsarraynoWords or phrases to search Threads for, up to 50.
max_posts_per_keywordintegernoPosts per keyword, up to 50 (Threads shows about 20 to 25). Default 25.
match_modestringnophrase, all_words, or off. Default phrase.
since_daysintegernoSet aside posts older than this many days.
min_likesintegernoSet aside posts with fewer likes.
include_repliesbooleannoReturn matching replies too. Default true.
only_newbooleannoSkip posts an earlier run returned. Default false.
state_keystringnoName for the only new posts memory.
max_charge_usdstringnoOptional cost cap for the run.
proxy_modestringnoauto or residential. Default auto.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
post-row, per Threads post that contains your keyword$0.0025$0.002375$0.00225$0.002125
apify-actor-start, per run start$0.0015$0.0015$0.0015$0.0015

Summary rows, refused input, posts set aside by your filters, and already delivered posts are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Full actor documentation

apify.com/mambalabs/threads-keyword-search

License

MIT. See LICENSE.

Source: README.md at commit f9611ee

Tools

1

search_threads_posts

Search Threads posts by keyword

Search Threads for keywords and return one flat row per post that contains the keyword: text, author, publish date, likes, replies, reposts, quotes, and the post link, plus one free summary row per keyword. By default a post is kept only when the keyword's words are in its text next to each other; a post found by several keywords is returned once. Threads shows a visitor who is not logged in about 20 to 25 posts per search. Reads the public Threads search page; no login or key. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN and is billed per post row.

Parameterskeywordsonly_newmin_likesstate_keymatch_modeproxy_modesince_daysmax_charge_usdinclude_repliesmax_posts_per_keyword

Version history

2
  1. v1.0.1LatestNov 5, 2026
  2. v1.0.0Nov 1, 2026

Score

90% 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 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts