Connect the RedReplier MCP server
RedReplier exposes a hosted MCP server that wraps the same public REST API. Use it when an AI client should manage websites, keywords, mentions, workspaces, and alert settings directly.
MCP URL: https://mcp.redreplier.com/mcp
Authentication
Point your MCP client at the URL and sign in when the browser opens. The server answers unauthenticated requests with a 401 and a WWW-Authenticate header, and OAuth-capable clients (Claude Code, Claude Desktop, ChatGPT, Cursor) open the RedReplier sign-in on their own. No API key to paste.
Prefer a key? Headless agents and clients without OAuth can send a RedReplier API token in the Authorization header instead. The server resolves the account from that token.
Client configuration
One-liner for Claude Code:
claude mcp add --transport http redreplier https://mcp.redreplier.com/mcpFull config for any MCP client:
{
"mcpServers": {
"redreplier": {
"type": "http",
"url": "https://mcp.redreplier.com/mcp"
}
}
}API key alternative, for headless agents and clients without OAuth:
{
"mcpServers": {
"redreplier": {
"type": "http",
"url": "https://mcp.redreplier.com/mcp",
"headers": {
"Authorization": "Bearer redreplier_your_key"
}
}
}
}Tools
| Tool | Arguments | Returns |
|---|---|---|
list_workspaces | No arguments | { workspaces: Workspace[] } |
list_websites | No arguments | { websites: Website[] } |
get_website | websiteId | Website |
create_website | url, optional name, keywords, description | Website |
update_website | websiteId, optional name, description | Website |
delete_website | websiteId | { deleted: true } |
analyze_website | url | { description: string } |
add_keywords | websiteId, keywords | Website |
edit_keyword | keywordId, value | Keyword |
disable_keyword | keywordId | Keyword |
enable_keyword | keywordId | Keyword |
delete_keyword | keywordId | { deleted: true } |
keyword_change_usage | No arguments | keyword edit usage |
list_mentions | optional websiteId, statuses, scoreBuckets, includeLowRelevance, minScore, keywords, sources, sort, from, to, limit, offset | paginated Mention[] |
count_mentions | optional websiteId, statuses, scoreBuckets, includeLowRelevance, minScore, keywords, sources, from, to | { total: number } |
update_mention_status | mentionId, status | Mention |
explain_mention | mentionId | Mention | null |
get_alert_settings | No arguments | alert settings |
update_alert_settings | enabled, optional cadenceMinutes | alert settings |
Notes
An OAuth sign-in can reach several workspaces. Call list_workspaces to list them, then pass the id as the optional workspaceId argument that every other tool takes. Without workspaceId, tools act in the default workspace.
Start with list_websites so the client knows the available websiteId and keywordId values. Keywords beyond the plan limit stay PENDING until a slot frees up. Disabling or deleting an active keyword, or deleting a website, frees a slot, and the oldest pending keyword that fits takes it. Only the user can change the plan, in the RedReplier app. delete_keyword works on a keyword in any status and also deletes its mentions, so confirm with the user first.
Troubleshooting
- A 401 on a request without a token is the OAuth challenge and is expected. Your client should open a sign-in window. A 401 with a token means the Bearer token is malformed, expired, revoked, or does not start with
redreplier_. - A 403 with
code: workspace_access_deniedmeans theworkspaceIdis not one this sign-in can reach; pick one fromlist_workspaces. A 403 withcode: subscription_requiredmeans the workspace plan does not include API access. A 403 withcode: permission_deniedmeans your role in that workspace does not holdredreplier.write, which Admin and Editor hold; ask a workspace admin for a role that does. - 404 errors usually mean the ID belongs to a different account group or was deleted.
- A keyword stuck in
PENDINGmeans the plan has no room for it. Ask the user to change the plan in the RedReplier app, or disable or delete another keyword.