Memo MCP Server
A filesystem-backed MCP server with REST API for AI tool integration and project workflow tracking. Zero database required.
README
Memo MCP Server
A filesystem-backed MCP server with REST API for AI tool integration and project workflow tracking. Zero database required.
Overview
This server uses your local filesystem as storage — no PostgreSQL, no Prisma, no external services. Data is stored as plain JSONL files in E:\.mcp\ and rules are read directly from E:\Data\*.md markdown files.
It provides a REST API on port 5000 and an MCP stdio interface that AI tools (Claude Desktop, Cline, etc.) can connect to directly.
Features
- Filesystem storage — plain JSONL files, readable in any editor
- REST API on port 5000 — full CRUD + keyword search on all entities
- MCP stdio server — AI tools call tools like
register_project,log_session,get_rulesdirectly - 123 rules loaded from
E:\Data\— engineering standards by domain (backend, frontend, database, infra, security, testing, teamwork) - Project session tracking — every Claude session logged and searchable
- Legacy CRM — companies, clients, memos (backward-compatible)
- Zero external dependencies — no database, no Docker, no cloud services
Getting Started
Prerequisites
- Node.js 18+
Setup
# Install dependencies
npm install
# Build
npm run build
# Start (REST API)
node dist/index.js
Usage
REST API
# Workflow: Projects & Sessions
curl http://localhost:5000/api/projects
curl -X POST http://localhost:5000/api/projects \
-H "Content-Type: application/json" \
-d '{"name":"my-app","techStack":"React,Node"}'
curl http://localhost:5000/api/sessions?projectName=my-app
curl -X POST http://localhost:5000/api/sessions \
-H "Content-Type: application/json" \
-d '{"projectName":"my-app","issue":"fixed login bug","rootCause":"missing JWT validation","solution":"added middleware"}'
# Rules
curl http://localhost:5000/api/rules?domain=backend
curl http://localhost:5000/api/rules/domains
curl http://localhost:5000/api/rules/search?keywords=caching
# Companies — full CRUD + search
curl http://localhost:5000/api/companies
curl http://localhost:5000/api/companies/search?keywords=acme
curl -X POST http://localhost:5000/api/companies \
-H "Content-Type: application/json" \
-d '{"name":"Acme Corp","country":"US","industry":"tech"}'
# Dashboard
curl http://localhost:5000/api/ai/summary
MCP (AI Tool Integration)
Run the server in MCP stdio mode:
$env:MCP_MODE="stdio"; node dist/index.js
Claude Desktop / Cline config
{
"mcpServers": {
"memo-server": {
"command": "node",
"args": ["E:\\mcp-server\\dist\\index.js"],
"env": {
"MCP_MODE": "stdio"
}
}
}
}
Available MCP Tools
| Tool | Description |
|---|---|
| Workflow | |
register_project |
Register a new project |
get_project_context |
Get project info + recent logs + relevant rules |
log_session |
Save structured session output |
search_sessions |
Search past work sessions |
get_rules |
Query rules by domain |
get_dashboard |
Overview of all projects and sessions |
| Legacy CRM | |
create_company |
Create a company record |
search_companies |
Search companies |
get_company / delete_company |
Get / delete by ID |
create_client / search_clients |
Client CRUD |
get_client / delete_client |
Client get / delete |
create_memo / list_memos |
Memo CRUD |
get_memo / delete_memo |
Memo get / delete |
ai_search / ai_context |
Cross-table search |
ai_quick_note / ai_summary |
Quick note / dashboard |
Data Storage
E:\
├── Data\development\*.md ← rules (edit to update standards)
├── Data\teamwork\*.md ← rules
├── mcp-server\ ← this repository
└── .mcp\ ← runtime data (auto-created)
├── projects\{name}\
│ ├── meta.json ← project info
│ └── sessions.jsonl ← session logs (append-only)
├── companies.jsonl ← CRM data
├── clients.jsonl
└── memos.jsonl
Architecture
The server reads E:\Data\*.md markdown files on startup, parses every ## section into a rule, and caches everything in memory. All writes use append-only JSONL files for O(1) write speed. No database, no ORM, no migrations.
Startup time: ~2ms.
Environment Variables
| Variable | Default | Description |
|---|---|---|
PORT |
5000 |
REST API port |
MCP_MODE |
— | Set to stdio for MCP protocol mode |
推荐服务器
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 模型以安全和受控的方式获取实时的网络信息。