Memo MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Memo MCP ServerRegister a new project called MyApp"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: todos
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_rulesdirectly123 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.jsUsage
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/summaryMCP (AI Tool Integration)
Run the server in MCP stdio mode:
$env:MCP_MODE="stdio"; node dist/index.jsClaude 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 a new project |
| Get project info + recent logs + relevant rules |
| Save structured session output |
| Search past work sessions |
| Query rules by domain |
| Overview of all projects and sessions |
Legacy CRM | |
| Create a company record |
| Search companies |
| Get / delete by ID |
| Client CRUD |
| Client get / delete |
| Memo CRUD |
| Memo get / delete |
| Cross-table search |
| 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.jsonlArchitecture
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 |
|
| REST API port |
| — | Set to |
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/devmaster-x/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server