Memoria MCP Server

Monorepo for Memoria MCP server, website, and API

Local serverstdio

What is the Memoria MCP server?

Most developer tooling work still happens through a UI a human drives. Memoria MCP server moves it into the conversation instead. Monorepo for Memoria MCP server, website, and API.

The short version

An MCP server that prevents your AI from breaking code by revealing hidden file dependencies through git forensics.

Getting it running

@byronwade/memoria on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

The tools it exposes

The server publishes 1 tool. What each one is for:

  • Evidence — Actual code diffs showing why files are related

What it needs from you

Configuration is passed through the environment: DATABASE_URL, STRIPE_KEY, STRIPE_SECRET. 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.

  • Node.js 18+ - Git repository with commit history - MCP-compatible AI tool ---

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • 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.

How it compares

Plenty of developer tooling 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. Memoria's toolset — Evidence — is a fair guide to whether it matches your workflow. It is maintained by byronwade; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
EvidenceActual code diffs showing why files are related

How to install the Memoria MCP server

{
  "mcpServers": {
    "memoria": {
      "command": "npx",
      "args": ["-y", "@byronwade/memoria"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 18+ - Git repository with commit history - MCP-compatible AI tool ---
VariableDescriptionRequired
DATABASE_URLEndpoint or connection string the server talks to.Yes
STRIPE_KEYCredential the server authenticates with.Yes
STRIPE_SECRETCredential the server authenticates with.Yes

Example prompts to try

  • Use Memoria to Evidence.

Frequently asked questions

It connects Memoria to MCP-compatible AI assistants such as Claude and Cursor, exposing 1 tool (Evidence) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Memoria directly.