mcp memory bank 1
A custom MCP server that allows storage, retrieval, and management of text-based information with natural language commands and keyword detection.
A custom MCP server that allows storage, retrieval, and management of text-based information with natural language commands and keyword detection.
A custom MCP (Model Capabilities Provider) server that functions as a persistent memory bank. This TypeScript-based server allows you to store, retrieve, and manage memories with flexible keyword detection and commands.
npm install
npm run build
Start the server with:
npm start
The server will begin listening on port 3000 by default.
GET /health
- Check server healthPOST /api/memories
- Store a new memoryGET /api/memories
- List or search memoriesGET /api/memories/:id
- Retrieve a specific memoryDELETE /api/memories/:id
- Delete a memoryPOST /api/detect
- Detect trigger keywords in textPOST /tools/list
- List available toolsPOST /tools/call
- Call a specific toolThe MCP server understands natural language commands related to memory management. Examples:
remember: This is important information I want to store
store: The meeting is scheduled for March 15th at 2pm
recall information about meetings
remember anything related to schedules
delete memory with id 5f4dcc3b5aa765d61d8327deb882cf99
forget id 5f4dcc3b5aa765d61d8327deb882cf99
list all memories
show all memories
├── dist/ # Compiled JavaScript output
├── logs/ # Log files
├── src/ # TypeScript source code
│ ├── config.ts # Server configuration
│ ├── index.ts # Entry point
│ ├── logger.ts # Logging configuration
│ ├── mcpServer.ts # Main MCP server implementation
│ └── memoryManager.ts # Memory storage and retrieval
├── package.json # Project dependencies
├── smithery.json # Smithery.ai configuration
├── tsconfig.json # TypeScript configuration
└── README.md # This file
Configuration is managed in src/config.ts
. The main settings include:
This MCP server is compatible with Smithery.ai deployments. To deploy:
smithery.json
file will guide the deployment processLogs are stored in the logs/
directory. All logs are formatted as JSON to ensure compatibility with the MCP specification.
ISC