How do I install Perenna?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Perenna need an API key?

The publisher lists these environment variables: PERENNA_GIT_REMOTE, VEXOR_API_KEY, VEXOR_REMOTE_RERANK_API_KEY, VEXOR_CONFIG_JSON.

What transport does Perenna use?

Perenna runs locally over stdio.

When was Perenna last checked?

Last checked 2026-10-28. A lightweight, Git-backed permanent memory for AI agents.

Perenna MCP サーバー

エージェントを強化

このサーバーを追加

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code PlugMCP で実行

キーとログ付きでコピーをホスト。

Local command

uvx perenna==0.4.1

Credentials from the publisher

PERENNA_GIT_REMOTE — Git remote name used for optional synchronization (for example, origin); leave unset for local-only operation
VEXOR_API_KEY — Embedding provider API key (optional; overrides a stored key; providers can also be configured via `vexor init`)
VEXOR_REMOTE_RERANK_API_KEY — Remote reranker API key (optional; overrides a stored key; only needed when rerank is set to remote)
VEXOR_CONFIG_JSON — Non-secret Vexor config as a JSON object, e.g. {"provider": "gemini", "rerank": "bm25"} (optional; merged over ~/.vexor/config.json; credential fields are rejected, use the dedicated variables)

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1PERENNA_GIT_REMOTE=<value> VEXOR_API_KEY=<secret> VEXOR_REMOTE_RERANK_API_KEY=<secret> VEXOR_CONFIG_JSON=<value> claude mcp add scarletkc-perenna -- uvx perenna==0.4.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "scarletkc-perenna": {4      "command": "uvx",5      "args": [6        "perenna==0.4.1"7      ],8      "env": {9        "PERENNA_GIT_REMOTE": "<value>",10        "VEXOR_API_KEY": "<secret>",11        "VEXOR_REMOTE_RERANK_API_KEY": "<secret>",12        "VEXOR_CONFIG_JSON": "<value>"13      }14    }15  }16}

claude_desktop_config.json

Local · pypiPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

PlugMCP で実行

キーとログ付きでコピーをホスト。

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

起動

Server facts

Local

Transport: stdio
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Perenna

A lightweight, Git-backed permanent memory for AI agents. Claude Code, Codex, ChatGPT, Cursor, and other MCP clients can share durable memories without sharing a vendor account or conversation history.

Separate MCP tools for reading, writing, and deleting memories
Local stdio, loopback-only Streamable HTTP, and OAuth-protected remote HTTP
Human-readable Markdown stored in an independent Git repository
Local Vexor retrieval index that can always be rebuilt from Git
Cross-process locking for multiple local agent processes

Why Perenna?

Your memory should follow you, not the agent you happen to be using.

Claude Code, Codex, Cursor, and ChatGPT keep memory in separate silos. Switch agents and your memory disappears. Switch machines and local memory stays behind.

Perenna gives them one shared, Git-backed memory. Local agents and ChatGPT can connect to the same self-hosted Perenna service, while every durable memory stays ordinary Markdown you can inspect, edit, version, and back up yourself.

Perenna stays focused on permanent memory: no required account, proprietary memory cloud, or automatic conversation extraction.

Quickstart

Install with your AI agent

Paste this into Claude Code, Codex, ChatGPT Desktop, Cursor, or another coding agent with terminal and local MCP configuration access:

Open the following URL, read the complete instructions, and follow them to
install and connect Perenna:
https://raw.githubusercontent.com/scarletkc/Perenna/main/docs/guides/agent-installation.md

Install a published release

Perenna requires Python 3.12+, Git, and uv.

Install Perenna

uv tool install perenna

Configure retrieval

Perenna needs a working Vexor embedding provider. For interactive provider selection and configuration, run:

uvx vexor init

Perenna automatically reuses ~/.vexor/config.json. When using process-level configuration, make sure the MCP server receives VEXOR_CONFIG_JSON plus VEXOR_API_KEY or the selected provider's key from its host environment. Remote providers receive memory text and search queries.

If you choose local embeddings, also install Perenna's local extra:

uv tool install "perenna[local]"

Vexor provider configuration covers remote and local setup. From the environment that starts the MCP client, verify the selected provider with:

uvx vexor doctor

Connect a client

For the standalone setup, configure the MCP client to start:

perenna mcp

Follow the Client setup guide for the exact client command or configuration file.

Codex and Claude Code can also install the optional memory behavior Skill:

perenna skill install --agent codex
# or
perenna skill install --agent claude-code

Repeat --agent in one command when both clients should receive the skill. The configuration reference documents user and project scope, destinations, and replacement safeguards.

Codex and Claude Code can instead install the combined Skill and MCP connection from Perenna's repository Marketplace. Follow the Plugin setup guide and choose one setup path per client.

Perenna creates its local data under ~/.perenna/ unless another home is configured.

Add optional Git synchronization

To import, publish, or fast-forward compatible history through a private Git repository, run:

perenna sync setup <repository-url>

Successful setup saves the selected remote in the Perenna home. Use perenna sync disable to return to saved local-only mode without removing the Git remote.

The configuration reference owns remote selection, credentials, conflict handling, and recovery details.

Install from source

git clone https://github.com/scarletkc/Perenna.git
cd Perenna
uv tool install .

Source contributors should use the locked environment in the development guide.

Documentation

Start with the documentation index, then follow the path for your task:

License

MIT