Skip to main content
Glama
Threads Keyword Search MCP Server

Threads Keyword Search MCP Server

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

Related MCP server: Threads API MCP Server

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:

{
  "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:

{
  "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.

Input

Type

Required

Description

keywords

array

no

Words or phrases to search Threads for, up to 50.

max_posts_per_keyword

integer

no

Posts per keyword, up to 50 (Threads shows about 20 to 25). Default 25.

match_mode

string

no

phrase, all_words, or off. Default phrase.

since_days

integer

no

Set aside posts older than this many days.

min_likes

integer

no

Set aside posts with fewer likes.

include_replies

boolean

no

Return matching replies too. Default true.

only_new

boolean

no

Skip posts an earlier run returned. Default false.

state_key

string

no

Name for the only new posts memory.

max_charge_usd

string

no

Optional cost cap for the run.

proxy_mode

string

no

auto or residential. Default auto.

Pricing

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

Event

Free plan

Bronze

Silver

Gold

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.

Available Tools

1 tool
search_threads_postsSearch Threads posts by keywordA
Read-onlyIdempotent

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.

Inputs: keywords, only_new, min_likes, state_key, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusing it with another tool. Its purpose—searching Threads posts by keyword—is clear and singular.

    Naming Consistency5/5

    The single tool name follows a clear verb_resource_action pattern (search_threads_posts) and uses consistent snake_case. There are no conflicting conventions to compare against.

    Tool Count4/5

    A single tool is slightly below the typical 3-15 range, but it fits the server's narrow, explicitly search-focused purpose. The tool is well-scoped and earns its place rather than being redundant.

    Completeness4/5

    The tool covers the core search operation with detailed post fields and a summary row, which is appropriate for a read-only keyword search server. Minor gaps include no pagination, date/author filters, or post-detail retrieval, but these are workable limitations for the stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Meta Threads by fetching profile details, recent posts, post and account analytics, and conversation reply trees, as well as exporting posts as JSON for archiving or embedding.
      7
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.
      30
      30 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Threads via MCP, including sub-80ms keyword search, full nested discussion tree extraction, replying to any external thread, publishing posts, fetching user profiles and threads, trending topics, and engagement actions like likes and reposts.
      3
      -