One session, start to finish
You do not pick the tools. You ask for what you want and the assistant chains them — this is a real Claude Code session, with the prompts written out so you can paste them.
- 01get_brand_context
“What ParseStream brand am I connected to, and which keywords are you tracking?”
The opening move of every session, and the fastest way to confirm the connection works. You get the brand, its competitors, every keyword with the platforms it runs on, and the credit balance — so nothing later in the chat is guessed.
- 02search_mentions
“Find mentions from the last 7 days that I haven't handled yet, relevance 4 or higher, where someone sounds like they're actively looking for a tool.”
That last clause is the whole product. The assistant turns it into intent filters — BUY_INTENT and PRODUCT_QUESTION — against a 7-day window, confident keyword matches only, and the untouched bucket. What comes back is a shortlist, not a firehose.
- 03get_mention
“Show me the second one in full — the whole comment, the upvotes, and whether there's already a draft for it.”
Search gives you enough to triage. Upvotes, subreddit size, the engagement-opportunity flag and whether a draft already exists only come back here, on the one mention you asked for.
- 04draft_reply
“Draft a short, value-first reply to it.”
The only step that costs anything: 5 credits, five to twenty seconds, and the text comes back in the chat. It is also saved to your Drafts queue. Nothing is posted anywhere.
- 05Your turn — no tool
(you read it, edit it, and post it from your own account)
This step is not automatable and is not meant to be. Open Replies in ParseStream, make it sound like you, and post it yourself on the platform it belongs to. No tool on this server can do it for you.
- 06mark_mention_replied
“Mark that one replied, and star the other three so I can come back to them tomorrow.”
The flags are the same ones the web app shows, so the queue you see tomorrow already reflects this conversation. Starring uses highlight_mention — and both take a mention out of the untouched bucket.
Six turns, six of the seven tools, one credit charge. Everything except the draft is free, and the only thing that ever reaches Reddit is the comment you post yourself from your Replies queue in ParseStream.
Seven tools
Four of them only read. Two set a flag on your own record of a mention. One writes a draft, and it is the only thing here that costs anything.
get_brand_contextFreeread-only- The whole workspace: brand profile and competitors, every tracked keyword with its ID and the platforms it is monitored on (paused ones included, flagged rather than hidden), the current credit balance and whether drafting is available at all.
search_mentionsFreeread-only- Searches your mentions across all five platforms. Filter by timeframe, platform, intent, relevance score, keyword, subreddit, mention type or status. Up to 30 per page, newest-posted first.
get_mentionFreeread-only- One mention in full: the untruncated body, the parent post title, the author, upvotes, subreddit size, the relevance score and intent tag, and whether a draft is already waiting for it.
draft_reply5 creditswrites a draft- Generates a reply draft for one mention and saves it to your Drafts queue. Pick the approach and the length, or let it use the brand's saved defaults. It returns text — a human still opens Replies, edits it and sends it.
mark_mention_repliedFreewrites a flag- Sets or clears the replied flag on one mention — the same toggle the web app shows. It moves the mention out of your new queue and leaves any existing draft alone.
highlight_mentionFreewrites a flag- Stars or unstars one mention, so a shortlist survives past the end of the chat. Starring also takes a mention out of the new queue — that filter means untouched, not unread.
get_brand_detailsFreeread-only- Brand name, description and website, and nothing else. One indexed row, back in milliseconds — the tool an assistant reaches for when all it needs to know is who it is working for.
Why is get_brand_details last? Because the tool list is served in a pinned order so the response is byte-identical between requests and clients can cache it. New tools get appended, never inserted — inserting one would invalidate every client’s cache from that entry on. Only draft_reply is billed, at 5 credits, and it needs an active subscription or trial; everything else works on any plan.
Connect your client
It is a remote server, so there is nothing to install and nothing to run locally. Mint a key under Brand Settings → API Keys, drop it into the block that matches your tool, and restart the client.
Keep the key out of your repository
Never run claude mcp add with -s project. That scope writes your key in plaintext into .mcp.json at the repo root — a file that exists to be committed and shared with your team, so a live key ends up in git history and, if the repo is public, in the hands of anyone who clones it. -s local (the default) stores it in your own user config outside the working tree. .cursor/mcp.json and .vscode/mcp.json are the same trap.
If a config genuinely has to be shared, put the variable in it rather than the key — the syntax differs per client, and Connecting without exposing your key has all four, plus 1Password and direnv. Already committed one? Revoke it first; rewriting history does not un-leak a secret.
Claude Code
one commandclaude mcp add --transport http parsestream https://mcp.parsestream.com/mcp \
--header "Authorization: Bearer ps_live_xxxxxxxxxxxxxxxx" \
-s localVerify with claude mcp list, or just ask the assistant which brand it is connected to.
Cursor
~/.cursor/mcp.json{
"mcpServers": {
"parsestream": {
"url": "https://mcp.parsestream.com/mcp",
"headers": {
"Authorization": "Bearer ps_live_xxxxxxxxxxxxxxxx"
}
}
}
}VS Code (GitHub Copilot)
.vscode/mcp.json{
"servers": {
"parsestream": {
"type": "http",
"url": "https://mcp.parsestream.com/mcp",
"headers": {
"Authorization": "Bearer ps_live_xxxxxxxxxxxxxxxx"
}
}
}
}VS Code is the odd one out: the top-level key is "servers", not "mcpServers". And .vscode/mcp.json is usually committed, so prefer ${env:PARSESTREAM_API_KEY} or your user-level config over a live key.
Codex CLI
~/.codex/config.toml[mcp_servers.parsestream]
url = "https://mcp.parsestream.com/mcp"
bearer_token_env_var = "PARSESTREAM_API_KEY"Codex stores the name of the variable rather than its value, so nothing key-shaped reaches the file. Export PARSESTREAM_API_KEY in your shell profile. To inline the key instead, the field is http_headers — not headers.
Grok
Grok has no connector directory, but it takes a bring-your-own server: at grok.com/connectors add a custom connector pointing at the endpoint above, with Bearer ps_live_… as the Authorization header. Grok's terminal agent reads Claude Code's MCP configuration, so if you ran the command above it is already connected there.
Claude Desktop and claude.ai
Claude Desktop and claude.ai have no one-click install yet — a listing in Anthropic's connector directory is planned, not shipped. Claude Code works today and is the fastest way to try this.
Connected? Ask your assistant “what ParseStream brand am I connected to?” — it should name your brand and list your tracked keywords. If it does not, the header is nearly always the cause; the full documentation has the troubleshooting list.
What it cannot do
Read-only by default, and the three tools that do write only touch your own rows. Worth stating plainly, because assistants sometimes say otherwise.
It never posts
No tool on this server publishes to Reddit, X, LinkedIn, Quora or Hacker News. The most it can do is write a draft into your own Drafts queue. If your assistant says it posted something, it did not.
It never contacts anyone
No DMs, no emails, no notifications to the people whose posts you are reading. Nothing on this server reaches a third party.
It only ever sees your brand
The brand comes from the API key, never from a tool argument, so cross-tenant access is impossible by construction. A mention belonging to someone else reports as not found, exactly like an ID that never existed.
It deletes nothing
The only writes are one reply draft and two boolean flags on your own mention rows. Four of the seven tools are read-only and cannot write at all.
A draft is not a reply
draft_reply returns text for a human to read, edit and send from their own account. That handoff is deliberate, and there is no tool that removes it.
Revoking a key cuts it off
Keys live under Brand Settings → API Keys, you can hold several per brand, and deleting one ends both MCP and REST access immediately. Reads work on any plan; drafting needs an active subscription and 5 credits.
Frequently Asked Questions
What is the ParseStream MCP server?
Which AI assistants can connect to it?
Can it post to Reddit or reply on my behalf?
How much does it cost to use?
How do I get an API key?
Is it safe to put my key in a project config file?
What are the rate limits and how far back can it search?
Why does search come back empty?
Where to go next
The long-form documentation, and the platform pages behind the mentions the server searches.
Full MCP documentation
Every tool argument, the credit and rate-limit rules, and the troubleshooting list — in the ParseStream help centre.
Reddit keyword monitoring
How the mentions get into ParseStream in the first place: round-the-clock Reddit tracking with AI relevance scoring.
X (Twitter) keyword monitoring
Tracking the same keywords on X, where the window to answer a post is measured in minutes.
LinkedIn keyword monitoring
Monitoring LinkedIn posts and comments for the phrases your buyers use.
Quora keyword monitoring
Catching the questions your product answers, on the site Google keeps ranking for them.
Hacker News keyword monitoring
Watching HN threads and comments for your product, your competitors and your category.
Point your assistant at your own mentions
Create a ParseStream account, mint a key under Brand Settings → API Keys, and paste one command into Claude Code. Reading costs nothing, and nothing on this server can post.
Free to try · No card to connect the server · Revoke the key any time