Records coding agent decisions and their constraints in a local SQLite database to track precedents and supersede old decisions.
Also known as LearningNodes/Elen, @learningnodes/elen-mcp
- Stars
- 4
- Tools
- 12
- Downloads, 30 days
- —
- Latest version
- 0.3.1
- Last commit
- Oct 20, 2026
- License
- AGPL-3.0
What is elen MCP?
elen records coding agent decisions and their constraints in a local SQLite database to track precedents and supersede old decisions. It exposes 12 tools, such as elen_commit, elen_get_competency, elen_consolidate.
Summary generated from the project's README
About elen MCP server
Elen provides a way for coding agents to maintain a memory of technical choices and the constraints that guided them. By using a local SQLite database, typically located at ~/.elen/decisions.db, the server allows agents to track precedents and update them when requirements change. This helps prevent agents from repeating past mistakes or ignoring established project rules.
Developers can integrate this server into various environments including Cursor, Claude Code, VS Code, and Gemini CLI using npx. The system works primarily in a local mode, though a connected mode requiring an API key is currently in beta. The server provides specific tools like elen_commit to save new decisions and elen_supersede to mark old ones as outdated.
To make the most of the server, users should include specific instructions in their system prompts. This ensures the agent uses elen_suggest to find existing precedents and elen_expand to view full details before committing to a new path. The toolset also includes elen_get_competency to show an agent's validated decision history.
What you can do with it
- 1Preventing repetitive technical errorsAn agent can search for previous technical choices to ensure a new decision does not conflict with established precedents.
- 2Updating outdated project rulesWhen a new requirement invalidates a previous choice, the agent can mark the old decision as superseded.
- 3Documenting technical constraintsA developer can instruct an agent to record specific limits, such as performance budgets, alongside every new decision.
Written from the project's README. Every use case is checked against a quote from it.
How to install elen MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall elen MCP in Claude Code
$ claude mcp add elen -- npx -y @learningnodes/elen-mcpInstall elen MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"elen": {
"command": "npx",
"args": [
"-y",
"@learningnodes/elen-mcp"
]
}
}
}Install elen MCP in VS Code
.vscode/mcp.json
{
"servers": {
"elen": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@learningnodes/elen-mcp"
]
}
}
}Install elen MCP in VS Code CLI
$ code --add-mcp '{"name":"elen","type":"stdio","command":"npx","args":["-y","@learningnodes/elen-mcp"]}'Install elen MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"elen": {
"command": "npx",
"args": [
"-y",
"@learningnodes/elen-mcp"
]
}
}
}Install elen MCP in Codex
$ codex mcp add elen -- npx -y @learningnodes/elen-mcpInstall elen MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.elen] command = "npx" args = ["-y", "@learningnodes/elen-mcp"]
Install elen MCP in Gemini CLI
$ gemini mcp add -s user elen npx -- -y @learningnodes/elen-mcpInstall elen MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"elen": {
"command": "npx",
"args": [
"-y",
"@learningnodes/elen-mcp"
]
}
}
}elen MCP tools 12
Detected from the READMEelen_commitelen_get_competencyelen_consolidateelen_get_contextelen_expandelen_incomingelen_log_decisionelen_search_precedentselen_statuselen_suggestelen_supersedeelen_team_search
| elen_commit | — | |
| elen_get_competency | — | |
| elen_consolidate | — | |
| elen_get_context | — | |
| elen_expand | — | |
| elen_incoming | — | |
| elen_log_decision | — | |
| elen_search_precedents | — | |
| elen_status | — | |
| elen_suggest | — | |
| elen_supersede | — | |
| elen_team_search | — |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHubElen is an open-source MCP server that records the decisions your coding agent makes, with the limits that bound them, and marks old decisions as superseded. It installs with one npx line, works with Cursor, Claude Code and any MCP client, and keeps decisions in a local SQLite file.
Install
npx -y @learningnodes/elen-mcp@0.3.1
Claude Code
claude mcp add --transport stdio elen -- npx -y @learningnodes/elen-mcp@0.3.1
VS Code
Open this link to install:
vscode:mcp/install?%7B%22name%22%3A%22elen%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40learningnodes%2Felen-mcp%400.3.1%22%5D%7D
Cursor
Add this to .cursor/mcp.json in your project:
{
"mcpServers": {
"elen": {
"command": "npx",
"args": ["-y", "@learningnodes/elen-mcp@0.3.1"]
}
}
}
Gemini CLI
Add this to settings.json (~/.gemini/settings.json, or .gemini/settings.json in your project):
{
"mcpServers": {
"elen": {
"command": "npx",
"args": ["-y", "@learningnodes/elen-mcp@0.3.1"]
}
}
}
Any other MCP client
Use the same mcpServers entry:
{
"mcpServers": {
"elen": {
"command": "npx",
"args": ["-y", "@learningnodes/elen-mcp@0.3.1"]
}
}
}
Tested with
| Client | Status |
|---|---|
| Claude Code | Run by the maintainer |
| Cursor | Configuration follows the client's documentation. Not yet recorded as tested. |
| VS Code | Configuration follows the client's documentation. Not yet recorded as tested. |
| Gemini CLI | Configuration follows the client's documentation. Not yet recorded as tested. |
| Other MCP clients | Configuration follows the client's documentation. Not yet recorded as tested. |
Make your agent use it
The tools alone give an agent no habit: it sees what each tool does, but it does not stop mid-task to ask whether a precedent exists. Add the block below to your rules file or system prompt so that searching before a decision and committing after one become part of every session.
# Epistemic Decision Memory Protocol
You must adhere to the Minimal Token Protocol for decisions:
1. Pointer-First Retrieval: Before making a technical decision, ALWAYS use elen_suggest to retrieve Top-K minimal pointers.
2. On-Demand Expansion: If a pointer looks relevant, you MUST call elen_expand on that specific ID. Do not hallucinate constraints.
3. Commiting Atoms: When deciding, use elen_commit. Summarize constraints into plain-text arrays (e.g. "budget < 500ms").
4. Graph Revision: If a decision invalidates a precedent, you MUST use elen_supersede to advance the graph state.
What it stores
In local mode decisions stay in a SQLite file on your machine (default ~/.elen/decisions.db). Connected mode is optional, needs elen login and an API key, and is in beta.
Tools
| Tool | What it does |
|---|---|
elen_commit |
Commits a new decision to the graph, with its constraints as a plain-text list. |
elen_get_competency |
Shows the competency profile for this agent, built from its validated decision history. |
elen_consolidate |
Suggests clusters and duplicate or stale candidates without changing the graph. |
elen_get_context |
Gives an overview of active decision threads grouped by domain, for the start of a session. |
elen_expand |
Expands a decision ID into its full constraints and text. |
elen_incoming |
Lists decisions other people have shared into your workspace. Connected mode, beta. |
elen_log_decision |
Creates a validated Decision Record from constraints, evidence and an answer. |
elen_search_precedents |
Searches validated decisions for precedents. |
elen_status |
Returns the agent, project, database path and counts, to check the namespace before committing. |
elen_suggest |
Retrieves short pointers to prior decisions before you make a new one. |
elen_supersede |
Revises an older decision and marks it superseded by a new one. |
elen_team_search |
Searches team and human decisions visible to your workspace for a topic. Connected mode, beta. |
Links
- Repository: https://github.com/LearningNodes/Elen
- Issues: https://github.com/LearningNodes/Elen/issues
- Discord: https://discord.gg/zJG6n2WGzM
- Licence: AGPL-3.0
Elen is the open-source part of Learning Nodes, the DecisionOps workspace. For the business decisions behind the code: https://workstation.learningnodes.com?utm_source=elen-readme&utm_medium=referral&utm_campaign=npm-page
elen MCP questions
How do I add elen MCP to Claude Code?
Run claude mcp add elen -- npx -y @learningnodes/elen-mcp in your terminal. Add --scope user to make it available in every project.
How do I add elen MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does elen MCP provide?
It exposes 12 tools, including elen_commit, elen_get_competency, elen_consolidate, elen_get_context, elen_expand.
Where are decisions stored?
Decisions are kept in a local SQLite file on your machine, defaulting to ~/.elen/decisions.db.
Does it work with Claude Code?
Yes, it is compatible with Claude Code and has been run by the maintainer.
How can I make my agent use elen?
You should add a specific 'Epistemic Decision Memory Protocol' block to your agent's rules file or system prompt to ensure it searches and commits decisions.
Is there a cloud or connected mode?
Yes, a connected mode is available in beta which requires an elen login and an API key.