Perenna MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

            result = subprocess.run(

        raw = yaml.load(frontmatter_text, Loader=_UniqueSafeLoader)

    private_key = directory / "id_ed25519"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

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 perenna -- uvx perenna

{
  "mcpServers": {
    "perenna": {
      "command": "uvx",
      "args": [
        "perenna"
      ]
    }
  }
}

[mcp_servers.perenna]
command = "uvx"
args = ["perenna"]

{
  "mcpServers": {
    "perenna": {
      "command": "uvx",
      "args": [
        "perenna"
      ]
    }
  }
}

{
  "servers": {
    "perenna": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "perenna"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: 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)).