redreplier
# RedReplier Agent
[](https://smithery.ai/servers/tarasshyn/redreplier)
Give your AI agent the ability to monitor **Reddit, Hacker News, X, and Bluesky** for keyword mentions of your product — and triage the AI-scored leads — from a single command.
**Works with:** Claude Code, Cursor, Windsurf, Codex, and any agent that supports skills.
## Install
```bash
npx skills add redreplier/agent
```
### Other installation methods
**Manual**: Copy the `skills/redreplier/` folder into your project's skills directory.
**Cursor remote rules**: Point to `https://raw.githubusercontent.com/redreplier/agent/main/skills/redreplier/SKILL.md`
## Setup
1. Create an account at [redreplier.com/signup](https://redreplier.com/signup)
2. Add the websites and keywords you want to monitor
3. Create an API token at [Settings → API Tokens](https://redreplier.com/api-tokens)
4. Run:
```bash
./scripts/redreplier.js setup --key redreplier_xxxxx
```
## What it does
Once installed, your AI agent can:
- **Manage monitored websites** — add, update, AI-analyze, remove
- **Manage keywords** — add, edit, enable/disable, activate within your plan
- **Triage mentions** — list AI-scored mentions from Reddit, Hacker News, X, and Bluesky, filter by relevance / keyword / source / date, approve or reject leads
- **Explain relevance** — see why a mention scored the way it did
- **Configure alerts** — enable email digests and set the cadence
## Example
```
You: Show me this week's best leads for my product.
Agent: 3 mentions scoring 70+. Top: r/webdev "Looking for an example tool" (85) —
a direct buying-intent question, plus one on Hacker News and one on X.
Want me to approve them and reject the rest?
```
## Alternative: MCP
For deeper integration with Claude Desktop, Cursor, or other MCP-compatible clients, use the RedReplier MCP server:
```json
{
"mcpServers": {
"redreplier": {
"type": "http",
"url": "https://mcp.redreplier.com/mcp",
"headers": {
"Authorization": "Bearer redreplier_your_key"
}
}
}
}
```
### Run it locally
The server source lives in [`mcp-server/`](./mcp-server). Run it over stdio with [Bun](https://bun.sh):
```json
{
"mcpServers": {
"redreplier": {
"command": "bun",
"args": ["run", "/path/to/agent/mcp-server/src/index.ts"],
"env": { "REDREPLIER_API_TOKEN": "redreplier_your_key" }
}
}
}
```
Or with Docker:
```bash
docker build -t redreplier-mcp .
docker run -i -e REDREPLIER_API_TOKEN=redreplier_your_key redreplier-mcp
```
## Links
- [RedReplier](https://redreplier.com)
- [API Tokens](https://redreplier.com/api-tokens)
- [MCP Server](./mcp-server)
## License
MIT
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action: website CRUD, keyword lifecycle, mention triage, alert settings, and billing previews are all cleanly separated. Overlapping actions like enable_keyword versus activate_pending_keywords are carefully disambiguated by scope and use case.
The overwhelming majority follow a consistent verb_noun pattern (list_websites, create_website, update_mention_status). Minor deviations like keyword_change_usage and preview_activate_pending break the pattern slightly but remain readable and predictable.
At 21 tools, the set is slightly heavy but each tool serves a real purpose in the website monitoring workflow. The billing and preview helpers add surface area but support the core keyword activation flow without being redundant.
The tool surface covers website lifecycle management, keyword CRUD and activation, mention retrieval and triage, alert configuration, and billing previews. There are no obvious dead ends: every state transition for websites, keywords, and mentions is supported by an appropriate tool.