Redlib MCP Server

If you already use Redlib, the redlib mcp server is the piece that lets your assistant work with it directly. MCP server for interacting with Redlib (private Reddit front-end).

What the server does

A Model Context Protocol (MCP) server that enables AI agents to interact with Reddit through your private Redlib instance. No Reddit API keys required - just a running Redlib instance!

• Privacy-First — - Uses your self-hosted Redlib, no tracking or API keys
• 3 Powerful Tools — - Search posts, get hot posts, fetch full post details with comments
• Docker Ready — - Both simple and hardened Docker images available
• Easy Setup — - Works with Claude Desktop, Cursor, VS Code, Codex, ForgeCode, KiloCode and any MCP-compatible client
• Structured Output — - Returns clean JSON instead of raw HTML

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Cursor — Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project level):
• ForgeCode — ForgeCode supports MCP servers via the forge mcp command for easy import
• KiloCode — The KiloCode tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: REDLIB_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Before using this MCP server, you need: 1. Redlib Instance - A running Redlib instance (default: http://localhost:8080) - Redlib GitHub - Redlib Docker Setup 2. MCP Client - One of: - Claude Desktop - Cursor - [VS

Where it fits

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Redlib's toolset — Cursor, ForgeCode, KiloCode — is a fair guide to whether it matches your workflow. It is maintained by devthatdoes; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.