In Memoria
About
Persistent codebase intelligence that gives agents memory across sessions.
Details
- Author
- pi22by7
- Downloads
- 382
- Categories
- Other, Developer Tools
Jump to
- Persists codebase knowledge across AI sessions
- Learns patterns, architecture, conventions, and decisions
- Integrates via the Model Context Protocol (MCP)
- Reduces token waste by avoiding re-analysis
- Eliminates repetitive explanations to AI assistants
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
In MemoriaCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install the npm package in-memoria and configure it as an MCP server for your AI coding assistant (e.g., Claude, Copilot, Cursor). Once configured, the server automatically learns from your codebase and provides context to the AI during sessions.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"in memoria": {
"in-memoria": {
"command": "npx",
"args": [
"in-memoria",
"server"
]
}
}
}
}
McpServers
{
"in-memoria": {
"command": "npx",
"args": [
"in-memoria",
"server"
]
}
}
In Memoria
Quick Demo
The Problem: Session Amnesia
You know the drill. You fire up Claude, Copilot, or Cursor to help with your codebase. You explain your architecture. You describe your patterns. You outline your conventions. The AI gets it, helps you out, and everything's great. Then you close the window. Next session? Complete amnesia. You're explaining the same architectural decisions again. The same naming conventions. The same "no, we don't use classes here, we use functional composition" for the fifteenth time. Every AI coding session starts from scratch. This isn't just annoying, it's inefficient. These tools re-analyze your codebase on every interaction, burning tokens and time. They give generic suggestions that don't match your style. They have no memory of what worked last time, what you rejected, or why.The Solution: Persistent Intelligence
In Memoria is an MCP server that learns from your actual codebase and remembers across sessions. It builds persistent intelligence about your code (patterns, architecture, conventions, decisions) that AI assistants can query through the Model Context Protocol. Think of it as giving your AI pair programmer a notepad that doesn't get wiped clean every time you restart the session.Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





