Context Engine
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
⚡ Context Engine
Persistent memory for AI coding agents.
A local-first MCP server for carrying useful context, decisions, and project history across AI sessions.
Quick start · Features · Tools · How it works · Configuration · Contributing
The problem
AI coding sessions are powerful—but context often disappears between conversations. Decisions get repeated, project history gets lost, and developers spend time re-explaining the same codebase.
Context Engine gives compatible AI clients a persistent, queryable memory layer. It is designed to keep useful project context available across sessions while giving developers ways to inspect, search, organize, and correct that memory.
Think of it as a memory layer for your AI workflow—not another chat interface.
Related MCP server: Jatobá Brain
✨ Why Context Engine?
🚀 Quick start
Requirements
Node.js 18 or later
An MCP-compatible client
Any additional credentials required by the features you enable
Use with Claude Desktop
Install Node.js if it is not already installed.
Open Claude Desktop's MCP configuration file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the following server entry:
{
"mcpServers": {
"context-engine": {
"command": "npx",
"args": [
"-y",
"-p",
"@sham-sundar-senthil-kumar/mcp-server@0.1.4",
"context-engine-mcp"
]
}
}
}If your configuration already has an mcpServers object, add only the "context-engine" entry inside it—don't overwrite your existing servers.
Save the file and fully restart Claude Desktop.
Open the MCP tools panel and check that Context Engine is available.
Tip: The first launch downloads the package through npm, so it may take a little longer than later launches.
Run it directly
You can also start the published server from a terminal:
npx -y -p @sham-sundar-senthil-kumar/mcp-server@0.1.4 context-engine-mcpThis starts an MCP server over standard input/output. It is intended to be launched by an MCP client; running it manually without sending MCP protocol messages will not open a chat UI.
🧰 Available tools
Context Engine exposes memory-management tools over MCP. The names below reflect the current tool interface; exact arguments and behavior are defined by the server implementation.
Tool | Purpose |
| Retrieve bounded saved context when starting a new session or restoring project context. |
| Inspect the memory graph, including branches, commits, and memory statistics. |
| Correct or prune a stored memory node. |
| Save an important decision, schema, or fix as a durable memory milestone. |
| Search past context and decisions using a query and supported scope. |
| Create an isolated memory branch for experimental work. |
| Merge changes from one memory branch into another. |
| Restore a previous memory state by selecting a commit. |
Example workflow
Start a new AI session and retrieve relevant context with
gather_context.Search for a past design decision with
recall.Record a completed architectural decision with
commit.Create a branch before exploring a risky refactor.
Review or correct saved context using
get_context_treeandoverride_memory_node.
Tool availability and required parameters depend on the server version and configuration. Consult the tool schemas exposed by your MCP client.
⚙️ How it works
flowchart LR
A["AI conversation"] --> B["Context Engine MCP server"]
B --> C["Capture and curate useful context"]
C --> D[("Local memory store")]
D --> E["Recall and inspect"]
E --> F["AI assistant uses relevant context"]
F --> G["Commit, branch, merge, or correct"]
G --> DThe goal is a hybrid-control workflow: make useful memory accessible by default, while preserving explicit tools for inspecting and changing what has been stored.
🔐 Privacy & data
Context Engine is designed around local-first use. However, local-first does not automatically mean every operation is offline or that no data ever leaves your device.
The MCP server runs in the environment where the client launches it.
Review the configured providers, API keys, and integrations before using sensitive project data.
Check the implementation and configuration to understand where memory is stored and whether any enabled model or embedding provider receives data.
Treat stored context as project data: protect your machine, backups, and credentials accordingly.
Before using this with confidential source code or personal information, review the data flow and provider settings for your specific setup.
📦 Packages & links
Resource | Link |
npm package | |
MCP Registry | |
Source code |
🧑💻 Development
Clone the repository:
git clone https://github.com/shamsundarsk/contextengine-.git
cd contextengine-
npm installBuild the MCP server:
npm run build -w packages/mcp-serverIf you're working on the core package as well, build it using the workspace script defined by the repository. The project uses a workspace layout, so run commands from the repository root unless a package script says otherwise.
🗺️ Roadmap
Potential areas for continued development:
Expand integration and client setup guides
Add end-to-end tests for core memory workflows
Document configuration and storage behavior in detail
Add troubleshooting guides and example workflows
Improve security, dependency auditing, and release automation
🤝 Contributing
Ideas, bug reports, documentation improvements, and pull requests are welcome.
Open an issue describing the use case or bug.
Keep changes focused and include reproduction steps for bug reports.
Add or update tests where appropriate.
Submit a pull request with a clear summary.
Please avoid including real API keys, private project data, or other secrets in issues and pull requests.
📄 License
Check the repository's LICENSE file for the applicable license.
Less re-explaining. More building.
Context Engine — persistent memory for the work behind your code.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Team memory for AI coding agents and code reviews, reviewed by humans and served over MCP.
Cross-tool persistent memory and context for AI assistants over MCP.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Persistent personal memory for AI assistants — save, search, and recall across every MCP client.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides a persistent, cross-tool memory layer for AI coding agents via MCP, enabling storage and retrieval of decisions, preferences, and context across different tools and models.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides persistent, multi-project memory for AI agents via MCP, enabling them to store and retrieve tasks, decisions, errors, checkpoints, and documentation while keeping context isolated by project.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain Git-backed long-term project memory over MCP, supporting on-demand retrieval, curated writes, conflict-safe versioning, idempotency, and crash recovery so new sessions or machines can recover context and continue working.6Apache 2.0