Generated banner for Mnemoverse Memory
Generated logo for Mnemoverse Memory

Mnemoverse Memory

Memory serverOfficial Mnemoverse project

Created by Mnemoverse

Published in mnemoverse/mcp-memory-server. Publisher page

28 GitHub stars

What it is

Hosted long-term memory for AI agents over MCP. Write and read memories from Claude Code, Cursor, VS Code and ChatGPT; rating a recalled memory as helpful or misleading re-ranks what comes back next. OAuth sign-in or API key, free plan.
— the description by Mnemoverse

AutoGineer overview, from the brain’s own files

Mnemoverse Memory is a hosted memory server that enables AI agents to persist information across different sessions and tools. By utilizing the Model Context Protocol (MCP), it allows agents in environments like Claude, Cursor, and VS Code to read and write to a centralized memory store. The system features a feedback mechanism where agents can rate recalled memories, which the server uses to re-rank future retrieval results. It also supports collaborative memory through shared rooms, allowing multiple users or agents to contribute to a common knowledge pool.

How it works

Memory model: Hybrid

AutoGineer overview, from the brain’s own files

The system acts as an MCP server that provides tools for agents to interact with a hosted memory database. Agents use memory_write to store information and memory_read to retrieve it using natural language. The server maintains a graph of associations between concepts. Users can create shared rooms for collaborative memory, and agents can provide feedback on the utility of retrieved information, which influences the ranking of future search results.

Folders
FolderRoleFiles
.githubagent-config8
docsdocs24
scriptsscripts11
srcsource-code15
testtests49

The agent reads

The agent writes

Requirements

Runtimes: Node.js >=18

Databases: PostgreSQL

API keys (by name): MNEMOVERSE_API_KEY

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Google Antigravity, Kiro, OpenCode, Amp, Roo Code, Cline, JetBrains Junie, Devin (ex-Windsurf)

Set it up

  1. Add mcp-memory-server to .mcp.json:

    {
      "mcpServers": {
        "mcp-memory-server": {
          "type": "http",
          "url": "https://mcp.mnemoverse.com/mcp"
        }
      }
    }
    
  2. Or add it with the Claude Code CLI:

    claude mcp add --transport http mcp-memory-server https://mcp.mnemoverse.com/mcp
  3. Your data is sent to mcp.mnemoverse.com.

  4. Add mnemoverse to .mcp.json:

    {
      "mcpServers": {
        "mnemoverse": {
          "type": "http",
          "url": "https://mcp.mnemoverse.com/mcp"
        }
      }
    }
    
  5. Or add it with the Claude Code CLI:

    claude mcp add --transport http mnemoverse https://mcp.mnemoverse.com/mcp
  6. Your data is sent to mcp.mnemoverse.com.

  7. Not scanned by AutoGineerIts dependencies are installed by npm when you run it and were not scanned by AutoGineer (2 declared). https://www.npmjs.com/package/@mnemoverse/mcp-memory-server
  8. Created by Mnemoverse. Published in mnemoverse/mcp-memory-server. Licence: MIT License.

Usage

AutoGineer overview, from the brain’s own files

  • Store project-specific preferences or coding patterns for future sessions.
  • Retrieve historical context when starting work on a previously touched project.
  • Collaborate with teammates by sharing a memory room.
  • Provide feedback on memory relevance to improve future retrieval accuracy.
“Save that we prefer using Vitest for testing in this project.”
The agent writes this preference to the memory server, making it available for future tasks.
“How do we usually handle authentication in this codebase?”
The agent queries the memory server and retrieves previously saved notes on authentication patterns.

Documentation by Mnemoverse

Read the documentation at the source

CODE_OF_CONDUCT.md

Contributor Covenant Code of Conduct

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people

  • Being respectful of differing opinions, viewpoints, and experiences

  • Giving and gracefully accepting constructive feedback

  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience

  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind

  • Trolling, insulting or derogatory comments, and personal or political attacks

  • Public or private harassment

  • Publishing others' private information, such as a physical or email address, without their explicit permission

  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at e-mail address on the upstream page. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

134 files · 124 not served here

Advantages

Limitations

Security

Risk level: Medium risk

This brain runs

Agent instructions that run or fetch something (14)

  • AGENTS.md: ChatGPT: install the published Mnemoverse Memory plugin and complete browser sign-in.
  • AGENTS.md: Per-client setup: https://mnemoverse.com/docs/api/install-by-host
  • AGENTS.md: Local stdio server: follow `llms-install.md`, which is written for an agent installing on a user's behalf.
  • AGENTS.md: Install with `npm ci`.
  • AGENTS.md: Build: `npm run build` (the prebuild step runs the config generator, the postbuild step regenerates `tools.json`).
  • AGENTS.md: Tests: `npm test` (vitest).
  • AGENTS.md: Test types: `npm run typecheck:test`.
  • AGENTS.md: Drift checks: `npm run verify:configs` (generated files match `src/configs/source.json`) and `npm run verify:tools` (committed `tools.json` matches the built server).
  • AGENTS.md: `src/configs/source.json` is the only file edited by hand for distribution metadata: descriptions, install snippets, env variables, registry fields.
  • AGENTS.md: `npm run generate:configs`
  • AGENTS.md: `npm run verify:configs`
  • AGENTS.md: A hand edit is overwritten on the next run and fails `verify-configs.yml` in the meantime.
  • AGENTS.md: For tool-description changes, run `npm run build` and commit the source plus regenerated `tools.json` and `manifest.json`.
  • AGENTS.md: Keep one concern per PR, run `npm test` and `npm run verify:configs` before pushing, and say in the description which of the checks above you ran.

MCP servers (11)

  • README.md (mnemoverse): npx -y mcp-remote@latest https://mcp.mnemoverse.com/mcp
  • README.md (mnemoverse): npx -y mcp-remote@latest https://mcp.mnemoverse.com/mcp
  • README.md (mnemoverse): https://mcp.mnemoverse.com/mcp · uses the network
  • README.md (mnemoverse): npx -y mcp-remote@latest https://mcp.mnemoverse.com/mcp
  • README.md (mnemoverse): npx -y mcp-remote@latest https://mcp.mnemoverse.com/mcp
  • README.md (mnemoverse): npx -y @mnemoverse/mcp-memory-server@latest
  • README.md (mnemoverse): npx -y @mnemoverse/mcp-memory-server@latest
  • README.md (mnemoverse): npx -y @mnemoverse/mcp-memory-server@latest
  • README.md (mnemoverse): npx -y @mnemoverse/mcp-memory-server@latest
  • README.md (mnemoverse): npx -y @mnemoverse/mcp-memory-server@latest
  • gemini-extension.json (mnemoverse): https://mcp.mnemoverse.com/mcp · uses the network
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:60)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:100)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:132)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:171)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:275)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:324)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:344)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:364)
  • Medium risk: runs-mcp-server-unpinned-runner (README.md:405)
  • Low risk: network-instructions (package.json:49)
  • Low risk: scripts-present (scripts/generate-configs.mjs)

Attribution and licence

Created by
Mnemoverse
Declared authors
  • Mnemoverse (declared in package.json)
Publisher
Mnemoverse (Official Mnemoverse project)
Source
mnemoverse/mcp-memory-server · commit 9fd95f6
Licence
MIT License (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Mnemoverse.

Install from source

124 of its files are not served here, so there is no ZIP. mnemoverse/mcp-memory-server at 9fd95f6