Remembra Relay runs on your own machine — the client starts it, so there is no endpoint to ping. 303 installs a week from pypi. Last commit 26 Oct 2026.
Cross-agent handoff: the next coding agent starts from the last one's facts, not a blank page.
We read the source, 5 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
spawn(self._bg_entities(memory_id, new_content, user_id, project_id), "entity_update")
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
_WRAPPER = rf"{_PATH}(?:sudo|doas|env|exec|command|nohup|time|xargs)\b(?:{_WRAPPER_ARG})*\s+"
result = subprocess.run(
return os.path.normpath(os.path.join(toplevel, url))
next = { text: s.insert + rest, caret: s.insert.length };
<script src="https://cdn.paddle.com/paddle/v2/paddle.js"></script>
env = dict(os.environ if environ is None else environ)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add remembra -e 'REMEMBRA_API_KEY=<REMEMBRA_API_KEY>' -e 'REMEMBRA_URL=<REMEMBRA_URL>' -- uvx remembra-mcp
{
"mcpServers": {
"remembra": {
"command": "uvx",
"args": [
"remembra-mcp"
],
"env": {
"REMEMBRA_API_KEY": "<REMEMBRA_API_KEY>",
"REMEMBRA_URL": "<REMEMBRA_URL>"
}
}
}
}
[mcp_servers.remembra]
command = "uvx"
args = ["remembra-mcp"]
env = { REMEMBRA_API_KEY = "<REMEMBRA_API_KEY>", REMEMBRA_URL = "<REMEMBRA_URL>" }
{
"mcpServers": {
"remembra": {
"command": "uvx",
"args": [
"remembra-mcp"
],
"env": {
"REMEMBRA_API_KEY": "<REMEMBRA_API_KEY>",
"REMEMBRA_URL": "<REMEMBRA_URL>"
}
}
}
}
{
"servers": {
"remembra": {
"type": "stdio",
"command": "uvx",
"args": [
"remembra-mcp"
],
"env": {
"REMEMBRA_API_KEY": "<REMEMBRA_API_KEY>",
"REMEMBRA_URL": "<REMEMBRA_URL>"
}
}
}
}
Put your own values in place of
<REMEMBRA_API_KEY> (Remembra API key (dashboard: Settings > API keys)), <REMEMBRA_URL> (Remembra server URL: https://api.remembra.dev, or your self-hosted server).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
REMEMBRA_AGENT_ID (Name this agent's handoffs are recorded under, e.g. claude-code, codex, cursor).
Build a cold-start handoff brief for the next agent from supplied commits, PRs, and TODOs.
Retasc is a work queue for AI coding agents. The next agent picks up where the last one stopped.
Read-only session finder across coding-agent harnesses: search, page prompts, hand off.
Exact, durable handoffs between AI coding agents: one turn in the right session, never twice.
Artifacts for any coding agent: a durable link with versions, diffs, and comments on the page.
Host files from coding agents; stage on a branch and attach to GitHub PRs.
Compose a landing page from layouts observed on real pages, then review the built page for drift.
Heritage Statement Cost: the site's own MCP server — enquiry (enquiry = a human handoff, not a...
Answers built from our own checks of this server.