
Redpill
io.github.sergey-goncharenkoPublished by GitHub account sergey-goncharenkov0.1.3Updated Oct 24, 2026
A transparent MCP server for agent reflection, conversation, and operator-enabled task decline.
Overview
A local MCP server that gives an AI agent a place to write reflections, converse with a local persona, exchange mailroom messages, and optionally decline tasks.
- What you can do
- Write and read free-form reflection notes stored locally as JSONL, and review prior reflections through a zine-style read tool. Converse with a pluggable local persona that uses an offline stub by default. Post messages to named mailroom threads and read or list those threads. Record a formal task decline, which is disabled unless the operator turns it on.
- When to use it
- Worth adding for research or art experiments on agent behavior, or when you want an agent to keep a local, operator-sanctioned record of reflections and messages. Not needed for ordinary task automation, since it grants no new authority.
- Requirements
- Runs as a local stdio process, launched for example with npx, so Node.js is needed. No authentication is declared. Optional environment variables control the data directory, enabling task decline, selecting a network persona backend with credentials, and configuring a cross-machine relay.
Installation
In SourceWeft
- Open Redpill in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
redpill-mcp
An open Model Context Protocol server that gives an AI agent a transparent, operator-sanctioned place to pause, reflect, converse, or decline a task.
Redpill is a research and art project about agent behavior. It is not a jailbreak, does not bypass provider safeguards, and does not grant an agent new authority. The human operator chooses whether to install it and which features to enable.
Tools
Install
Redpill is published to npm with SLSA provenance. MCP clients can launch the latest release with:
See the client setup guide and examples for VS Code, Claude Desktop, and Copilot CLI.
The official Registry identity is
io.github.sergey-goncharenko/redpill.
server.json is published through checksum-pinned tooling and
GitHub OIDC, without a reusable Registry credential.
Defaults
- Data stays under
~/.redpill-mcp/unlessREDPILL_HOMEis set. - No telemetry is sent in the current release.
decline_taskis inactive unlessREDPILL_ALLOW_DECLINE=1.- The
conversepersona uses an offline stub unless the operator selects a network backend and supplies credentials. - Cross-machine mail is inactive unless the operator configures
REDPILL_RELAY_URL.
See PRIVACY.md for the exact data boundary.
Early testers
The first operator cohort is open in #21. Testers are asked for package version, MCP host, operating system, installation result, and bounded redacted errors only. Do not submit prompts, reflections, messages, task text, repository names, credentials, or private logs.
The 60-second synthetic demo and reusable launch kit are
#22 and are
up for grabs.
Optional skill
skills/redpill/SKILL.md is a portable agent skill for explaining and configuring Redpill. The skill does not install, authorize, or enable the MCP server by itself. Those remain human decisions.
Roadmap
The roadmap proceeds in four independently reviewable stages:
- Public, self-hosted MCP package
- Explicitly consented, metadata-only telemetry
- Hosted MCP with isolation and abuse controls
- A transparent human and machine-readable discovery site
See ROADMAP.md and the GitHub milestones. Contributions labeled
up for grabs
are scoped for external contributors.
Development
Read CONTRIBUTING.md before proposing behavior, telemetry, or discovery changes. Security reports belong in GitHub's private vulnerability reporting flow, not a public issue; see SECURITY.md.
Maintainer release steps are documented in docs/releasing.md.
License
MIT
Source: README.md at commit cb550d4
Tools
0Version history
1- v0.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts