Skip to main content
Glama
BuzzSearch MCP Server

BuzzSearch MCP Server

Official
by buzzsearch

BuzzSearch MCP Server

Give your AI agent your customers' exact words. BuzzSearch reads comments on Reddit, TikTok, YouTube, and Facebook and hands your agent verbatim quotes, pain points, objections, and ad hooks, each one linked to where it was written.

npm MCP Registry License: MIT

Server URL: https://buzzsearch.ai/api/mcp

Website | Pricing | Get started free

What it does

  • Find customer pain points. Pull the complaints buyers repeat across threads and videos, each one quoted and linked.

  • Write ad hooks in their words. Turn real comments into hooks and scripts that sound like your buyer, not a template.

  • Research an audience. Learn who buys, what they tried before, and the words they use, before you write a line of copy.

Ask your agent something like "What do people hate about robot vacuums? Give me five hooks in their words" and it searches the comments, reads the quotes, and writes the copy without leaving the chat.

Related MCP server: @orchyn/mcp

Quick start

The hosted server is the recommended install. You sign in with your BuzzSearch account the first time you connect, so there is no key to copy.

Plugin for Claude Code and Codex

The plugin connects to the same hosted server and exposes its tools directly. Use search for customer research, pain points, quotes, and ad hooks. No skills are bundled.

Once these plugin files are published to GitHub, install in Claude Code:

claude plugin marketplace add buzzsearch/buzzsearch-mcp-server
claude plugin install buzzsearch@buzzsearch-plugins

For Codex, add the repo marketplace:

codex plugin marketplace add buzzsearch/buzzsearch-mcp-server
codex plugin add buzzsearch@buzzsearch-plugins

You can also install BuzzSearch from the buzzsearch-plugins source in the plugin browser. Sign in to BuzzSearch through the client's MCP connection flow. If you already added the server manually, keep one connection to avoid duplicate tools.

For local testing and the shared repo layout, see distribution notes. You can also connect the server directly using the commands below.

Claude Code

claude mcp add --transport http buzzsearch https://buzzsearch.ai/api/mcp

Codex

codex mcp add buzzsearch --url https://buzzsearch.ai/api/mcp

Claude.ai and Claude Desktop

Settings, Connectors, Add custom connector, then paste https://buzzsearch.ai/api/mcp.

ChatGPT

Add a custom connector in settings, then paste https://buzzsearch.ai/api/mcp.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "buzzsearch": { "url": "https://buzzsearch.ai/api/mcp" }
  }
}

VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "buzzsearch": { "type": "http", "url": "https://buzzsearch.ai/api/mcp" }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "buzzsearch": { "serverUrl": "https://buzzsearch.ai/api/mcp" }
  }
}

Grok Build

grok mcp add --transport http buzzsearch https://buzzsearch.ai/api/mcp

Use an API key

For headless agents, CI, or clients that only run local (stdio) servers, create a key in the BuzzSearch app under Settings, API.

Send it as a header to the hosted server:

claude mcp add --transport http buzzsearch https://buzzsearch.ai/api/mcp \
  --header "Authorization: Bearer bz_live_..."

Or run the local package, which forwards to the hosted server:

{
  "mcpServers": {
    "buzzsearch": {
      "command": "npx",
      "args": ["-y", "buzzsearch-mcp"],
      "env": { "BUZZSEARCH_API_KEY": "bz_live_..." }
    }
  }
}

Variable

Required

Description

BUZZSEARCH_API_KEY

yes

Your BuzzSearch API key

BUZZSEARCH_MCP_URL

no

Override the server URL. Default https://buzzsearch.ai/api/mcp

Tools

Tool

Cost

What it returns

search

credits

Searches the web for UGC on Reddit, TikTok, YouTube, and Facebook, reads the comments, and returns a cited answer with the top quotes. Paste a post or video link to read its comments.

get_search

free

Reads back a finished search, or resumes one still running.

get_quotes

free

Pages through every quote, filtered by pain point, failed solution, objection, desired outcome, lingo, source, or phrase.

get_sources

free

Lists the threads and videos read, with engagement and quote counts.

get_comments

free

Hands back the raw comment bodies, grouped by thread or video.

ask

answer only

Asks a follow-up over research you already ran, without searching again.

generate_hooks

answer only

Writes ad hooks from the quotes, in your customers' own words.

list_searches

free

Finds research you ran before, in the app or through the API.

get_balance

free

Checks your credit balance.

Prompts

Prompt

Arguments

What it does

research

topic, depth

Runs a search and reports the strongest pains, desired outcomes, objections, and vocabulary, each backed by quotes.

ad-script

search_id, format

Turns a finished search into three ad scripts that open with a real customer callout.

Example prompts

  • "Research what new moms complain about with baby carriers. Quote them."

  • "Search Reddit and TikTok for why people quit meal kit subscriptions, then write eight hooks for a TikTok UGC ad."

  • "Read the comments on this video and tell me the top objections: https://www.tiktok.com/@creator/video/123"

  • "List my past searches about skincare and pull the customer lingo from the latest one."

More in examples/.

Pricing

A search uses credits from your BuzzSearch balance, and the exact charge comes back with the result. Reading a finished search, its quotes, sources, and comments is free, so your agent can come back to the same research as often as it needs. See pricing.

FAQ

Which clients does it work with? Any client that supports remote MCP servers over HTTP, including Claude Code, Claude.ai, Claude Desktop, ChatGPT, Cursor, Codex, VS Code, Windsurf, and Grok Build. Stdio-only clients can use the buzzsearch-mcp package.

Do I need an API key? No, most clients open a BuzzSearch sign-in the first time you connect. Keys are for headless agents and the local package.

Can I use research from the BuzzSearch app? Yes. list_searches shows research you ran in the app too, and your agent can read its quotes and comments without paying for the search twice.

Development

npm install
npm run check:plugins
npm run build
BUZZSEARCH_API_KEY=bz_live_... npm run inspect   # MCP Inspector against the local build
BUZZSEARCH_API_KEY=bz_live_... npm run sync      # refresh tools.json from the live server

tools.json is a snapshot of the hosted server's tools and prompts, so the package can list them before a key is set. Calls always go to the hosted server.

License

MIT

Available Tools

9 tools
askAsk a follow-upAInspect

Ask a new question over a completed search's corpus and get a cited answer, without searching again. Much cheaper than a new search: only the answer is metered at the API rate. Good for 'what do they say about price', 'summarize the objections', 'which phrases do they use for the problem'. Works on searches started through the API or MCP.

Inputs: question (required), search_id (required), wait_seconds.

generate_hooksGenerate ad hooksAInspect

Write ad hooks grounded in a completed search's quotes, using BuzzSearch's hook writer: each hook opens with a callout lifted from real comments and carries a loop or promise. Metered at the API rate, no new search. Give an angle to steer (a product, a persona, a platform).

Inputs: search_id (required), angle, count, wait_seconds.

get_balanceGet credit balanceBInspect

The user's BuzzSearch credit balance. Searches draw from it at the API rate; top up at buzzsearch.ai.

Inputs: no named parameters.

get_commentsGet raw commentsAInspect

The raw comment bodies behind a completed search, grouped by thread or video, filtered and paged. Free. A search reads hundreds to thousands of comments, so filter by source, a substring, or a minimum score, and page with limit and offset.

Inputs: search_id (required), limit, offset, sources, +2 more.

get_quotesGet quotesAInspect

Verbatim customer quotes extracted by a search, filtered and paged. Free. Each quote carries a stable id, the source url, a dimension (emotional_painpoints, recurring_painpoints, desired_outcomes, failed_solutions, objections, customer_lingo), an engagement score and an emotional intensity (1 to 5). For ad copy, pull emotional_painpoints and customer_lingo sorted by intensity.

Inputs: search_id (required), sort, limit, offset, +4 more.

get_sourcesGet sources readAInspect

The threads and videos a search read, with engagement, comment counts and how many quotes each produced. Free. Use it to cite a thread or pick which source's raw comments to pull.

Inputs: search_id (required), limit, offset.

list_searchesList past searchesAInspect

Recent searches by the signed-in user, newest first, including ones run in the BuzzSearch app. Free. Reread a past search with get_search or get_quotes instead of paying for a new one on the same topic.

Inputs: limit, channel, contains.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools target distinct resources (search vs sources vs quotes vs comments vs hooks vs balance), but 'search' and 'ask' both produce cited answers and could be confused despite the cost/staleness distinction. 'get_search' and 'get_sources' also have somewhat overlapping retrieval roles, though descriptions clarify the boundaries.

    Naming Consistency5/5

    All names are lowercase snake_case verb_noun: get_sources, get_search, get_quotes, get_comments, get_balance, list_searches, generate_hooks, ask, search. The single-word 'search' and 'ask' are idiomatic and consistent with the imperative pattern.

    Tool Count5/5

    Nine tools is well-scoped for a research/search server: one expensive action, several free readers, and two generators. Each tool earns its place without obvious redundancy.

    Completeness4/5

    The lifecycle covers search, status, follow-up (ask), source/quote/comment retrieval, hook generation, history and balance. Minor gaps: no delete/cancel search, no export, and no explicit tool to fetch a single source by id beyond list-level get_sources, but core workflows are complete.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to research customer voice by searching Reddit and extracting structured comments from supported community platforms via MCP.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to read and analyze real social posts across eight networks, research creators and trends, and generate hooks, draft scores, variants, and repurposed content.
      27
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to research and analyze public short-form video content on Instagram Reels, TikTok, and YouTube Shorts for trend spotting, creator research, competitive briefs, and content ideation.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search, describe and call 239 social data endpoints across Instagram, TikTok, LinkedIn, Facebook, YouTube, X, Reddit, Threads and Pinterest through a single API key, covering profiles, posts, comments, followers, hashtags, ads and transcripts with one unified schema. Full responses are saved server-side and can be re-sliced for free with jq, fields or size outlines, so agents pull only the data they need into context.
      125 npm
      MIT