de_tutor_read_memoryLABSCO SUMMARY
The memory is just a JSON file.
Known concepts live in data/data-engineering-knowledge.json, which means you can read it, edit it and check it into a repo — and also that there is one profile per checkout and no concurrency story. If Cursor does not pick up the server's prompt automatically, the README's fallback is to paste the same guidance into a project rule file and reference it in your request.
What it is
A tutor server that fetches recent data-engineering developments and filters them against a stored profile of what you already know, so the assistant tells you about the parts that are new to you.
What you get
de_tutor_get_updatesqueries Perplexity through OpenRouter for recent data-engineering news, patterns and technologiesde_tutor_read_memoryreturns the concepts already marked as knownde_tutor_write_memorymarks a concept as known or unknown, taking aconceptand aknownboolean- A
data_engineering_knowledge_memoryresource backing all of it — a JSON object mapping concept names to booleans - A
data-engineering-tutor-guidanceprompt that tells the client the intended order: fetch updates, read memory, present what is new, then update memory from your answers
Requirements
Build from source: npm install then npm run build, and launch build/index.js with node using an absolute path. The project is data-engineering-tutor, version 1.0.0, and the binary name is de-tutor. Node.js v18 or later. de_tutor_get_updates needs an OpenRouter API key in OPENROUTER_API_KEY, either in a .env file at the project root or in the client's env block. The other two tools need no key.
Setup effort
Build from source — git clone https://github.com/scriptstar/de-mcp-server.git
USE CASES
Getting a briefing that skips what you already know
Fetch recent developments, compare against your stored profile, and hear only the unfamiliar parts.
Recording that you have learned something
Mark a concept as known so it stops appearing in future briefings.
Auditing what the tutor thinks you know
Read the profile back and correct entries that are wrong.
3 tools
Listed in project docs. Your client may show a different list.
de_tutor_write_memoryde_tutor_get_updatesBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
- Node.js
- OPENROUTER_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/scriptstar/de-mcp-server.git
cd de-mcp-server
npm install
npm run buildMCP Clients
Claude Desktop, Cursor
{
"mcpServers": {
"de-tutor": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DE_MCP_SERVER>/build/index.js"
],
"env": {
"OPENROUTER_API_KEY": "<YOUR_OPENROUTER_API_KEY>"
}
}
}
}