ParseStream MCP server

ParseStream MCP Server

ParseStream watches Reddit, X, LinkedIn, Quora and Hacker News for mentions of your brand, scores each one for relevance and buying intent, and writes reply drafts. This server hands that to your AI assistant: ask what people said about you this week, which of those sound like someone shopping for a tool, pull one up in full, and get a draft back that you edit and send yourself.

Nothing here can post. There is no tool on this server that publishes to Reddit, X, LinkedIn, Quora or Hacker News, or that contacts anyone.

It is a remote server — nothing to install or run locally, just a URL and an API key.

Get an API key first

In ParseStream, go to Brand Settings → API Keys and create one. It starts with pslive and is shown exactly once, so copy it straight into your client config.

A key is scoped to a single brand — the server never reads arguments to decide whose data you get, only the key. To connect a second brand, mint a second key and add it as a second MCP server under a different name. Revoking a key in Brand Settings cuts off MCP access immediately.

It is the same key the Mentions REST API uses, and both share one budget: 100 requests per minute per key. Every JSON-RPC call counts, including the tools/list your client fetches on connect. Over the limit you get a 429 with a Retry-After header.

Install

Replace pslivexxxxxxxxxxxxxxxx with your own key in whichever block matches your tool, then restart the client. Every one of these clients can read the key from an environment variable instead of holding it in the file — see Connecting without exposing your key, and read it first if any of these files lives inside a repository.

Claude Code

claude mcp add --transport http parsestream https://mcp.parsestream.com/mcp \
  --header "Authorization: Bearer ps_live_xxxxxxxxxxxxxxxx" \
  -s local

[!WARNING]

Keep -s local. The -s project scope writes your key in plaintext into .mcp.json

at the repo root — a file meant to be committed and shared with your team. A live

ParseStream 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 repository, scoped to this project; -s user does the same but makes the

server available in every project. Neither puts anything in the working tree. If your

team genuinely needs a shared .mcp.json, put the variable in it rather than the

key — below.

Shortened. The full README is on GitHub.