Recall — Memory Agent for Students
Enables students to capture and recall narrated observations from labs, lectures, or fieldwork, and generate study summaries or lab report drafts.
README
🧠 Recall — Memory Agent for Students
Amrita University MCP Hackathon 2026
Track: Education & Research
Team Members: [Insert Names & Roll Numbers]
Deployed URL: [Insert Nitrostack URL]
Demo Video: [Insert Video Link]
Problem & Solution
Recall is an MCP (Model Context Protocol) server that acts as a persistent memory agent for students. It captures narrated observations during labs, lectures, or fieldwork, stores them as structured, searchable memory, and lets the student — or an AI study assistant — recall them later across sessions.
Example: A chemistry student narrates "this is the titration setup for experiment 3, the flask needs to sit for 10 minutes" during a lab. Later, they (or their AI assistant) can recall that observation, get a study summary, or generate a lab report draft — all from the MCP server.
🏗 Architecture
Built with the NitroStack MCP framework using a NestJS-style modular architecture:
recall/
├── src/
│ ├── index.ts # Bootstrap entry point
│ ├── app.module.ts # Root @McpApp module
│ └── modules/
│ ├── storage/
│ │ ├── storage.module.ts # Global storage module
│ │ └── database.service.ts # SQLite wrapper (sql.js)
│ └── recall/
│ ├── recall.module.ts # Feature module
│ ├── recall.tools.ts # 5 MCP tools
│ ├── recall.resources.ts # Session graph resource
│ ├── recall.prompts.ts # 2 prompt templates
│ ├── observation.service.ts # Business logic service
│ └── types.ts # TypeScript interfaces
├── data/ # SQLite DB (auto-created)
├── package.json
├── tsconfig.json
├── .env / .env.example
└── README.md
🔌 MCP Primitives
Tools (5)
| Tool | Description |
|---|---|
capture_observation |
Store a new observation with label, note, context, and session ID |
recall |
Search observations by keyword, optionally scoped to a session |
update_observation |
Edit an existing observation's note |
delete_observation |
Soft-delete an observation |
list_sessions |
List all sessions with counts and date ranges |
Resources (1)
| URI | Description |
|---|---|
recall://sessions/{session_id}/graph |
Read-only structured dump of all observations in a session with inferred relations |
Prompts (2)
| Prompt | Description |
|---|---|
study_summary |
Generates a concise study summary from session observations |
lab_report_draft |
Turns session observations into a structured lab report skeleton |
🚀 Getting Started
Prerequisites
- Node.js ≥ 20.18.1 (use nvm to manage versions)
- npm ≥ 9
- tsx installed globally:
npm i tsx -g
Install & Run
# 1. Install dependencies
npm install
# 2. Start the dev server
npx @nitrostack/cli dev
The server starts in stdio mode, ready for any MCP client (NitroStudio, Claude Desktop, etc.) to connect.
Environment Variables
Copy .env.example to .env and adjust if needed:
DB_PATH=./data/recall.db
The SQLite database and data/ directory are created automatically on first run.
📋 Example Usage Flow
1. Capture observations during a lab
→ capture_observation({
label: "titration setup",
note: "Flask with 25ml NaOH, add phenolphthalein indicator, 3 drops",
context: "experiment-3",
session_id: "chem-lab-2026-07-18"
})
← { id: "abc-123", timestamp: "2026-07-18T10:30:00Z" }
→ capture_observation({
label: "titration endpoint",
note: "Color changed from pink to colorless at 22.4ml HCl",
context: "experiment-3",
session_id: "chem-lab-2026-07-18"
})
← { id: "def-456", timestamp: "2026-07-18T10:45:00Z" }
2. Recall observations later
→ recall({ query: "titration", session_id: "chem-lab-2026-07-18" })
← { count: 2, results: [ ... ] }
3. Browse session graph
→ read resource: recall://sessions/chem-lab-2026-07-18/graph
← { observations: [...], relations: [...], metadata: { ... } }
4. Generate a study summary
→ use prompt: study_summary({ session_id: "chem-lab-2026-07-18", topic: "titration" })
← [Formatted prompt with observations embedded, asking AI to produce a study summary]
5. Draft a lab report
→ use prompt: lab_report_draft({ session_id: "chem-lab-2026-07-18" })
← [Formatted prompt asking AI to produce Objective → Method → Observations → Conclusion]
🏆 Hackathon Rubric Alignment
| Criterion | How Recall Addresses It |
|---|---|
| MCP Primitives | All 3 implemented: Tools (5), Resources (1), Prompts (2) |
| Education & Research | Memory agent designed for students in labs, lectures, fieldwork |
| Code Quality | TypeScript strict mode, NitroStack decorators, DI, modular architecture |
| Architecture | Clean separation: storage → service → tools/resources/prompts |
| Runnable Locally | npm install && npx @nitrostack/cli dev — zero external dependencies |
| Storage | SQLite via sql.js (WASM-based, auto-schema, swappable) |
🔮 Future Enhancements (if time allows)
- Semantic similarity search (embeddings + vector store)
- Camera/mic streaming for real-time observation capture
- Canvas UI for visual browsing of observation graphs
- Notion/Slack/Gmail integrations for exporting summaries
- Graph DB backend (Neo4j/SurrealDB) for richer relation queries
📄 License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。