Pirelli71/knoco-mcp
If you are the rightful owner of knoco-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Knoco MCP Server is a Memory Capabilities Provider that integrates with mem0 for consultant-specific memory management.
Knoco MCP Server
Memory Capabilities Provider (MCP) server for Knoco that integrates with mem0 for consultant-specific memory management.
Overview
The Knoco MCP Server provides memory capabilities to various environments including Claude Desktop, VS Code, Cursor, and others. The server acts as a bridge between these environments and the mem0 memory system, allowing for the storage, retrieval, and management of consultant-specific memories.
Features
- Memory Management: Add, search, retrieve, and delete memories
- Chat Processing: Automatically extract memories from conversations
- Consultant-Specific Memory Types: Support for decisions, issues, actions, client context, etc.
- Multi-Environment Support: Integration with Claude Desktop, VS Code, Cursor, and more
- API-Based Integration: Modular design with mem0 API integration
Installation
See the for detailed setup instructions.
Architecture
The server follows a modular architecture:
┌────────────────────────────────────────────────────────┐
│ Client Environments │
│ (Claude Desktop, VS Code, Cursor, Other MCP Clients) │
└────────────────────────┬───────────────────────────────┘
│ MCP Protocol
▼
┌────────────────────────────────────────────────────────┐
│ Knoco MCP Server (FastAPI) │
├────────────────────────────────────────────────────────┤
│ ┌────────────────┐ ┌────────────────┐ ┌─────────────┐ │
│ │ MCP Endpoints │ │Memory Extractor│ │Memory Router│ │
│ └───────┬────────┘ └───────┬────────┘ └──────┬──────┘ │
│ │ │ │ │
│ ┌───────┴───────────────────┴─────────────────┴──────┐ │
│ │ mem0 API Client │ │
│ └────────────────────────────┬─────────────────────┬─┘ │
└─────────────────────────────┬┴─────────────────────┴──┘
│
┌─────────────────────────────┼────────────────────────┐
│ mem0 Memory System │
├─────────────────────────────┴────────────────────────┤
│ │
│ ┌─────────────────┐ ┌──────────────────────┐ │
│ │ Memory Storage │ │ Embedding Generation │ │
│ └─────────┬───────┘ └─────────┬────────────┘ │
│ │ │ │
│ ┌─────────┴───────────┐ ┌─────────┴────────────┐ │
│ │ PostgreSQL/pgvector │ │ LLM Provider │ │
│ └─────────────────────┘ └────────────────────┬─┘ │
└───────────────────────────────────────────────┬──────┘
│
┌───────────────────────────────────────────────┼──────┐
│ External Services │
│ (OpenAI, Claude, etc.) │
└───────────────────────────────────────────────────────┘
API Endpoints
The MCP Server exposes a set of endpoints following the MCP protocol:
-
Memory Management:
/memory/add: Add a new memory/memory/search: Search for relevant memories/memory/get/{id}: Retrieve a specific memory/memory/delete/{id}: Delete a specific memory
-
Chat Processing:
/chat/process: Process a chat history for automatic memory extraction
-
MCP Protocol:
/mcp-info: Information about the MCP server/capabilities: Available capabilities
Configuration
Configuration is managed through environment variables or configuration files:
- mem0 Configuration: API keys, base URL, embedding model, etc.
- MCP Server Configuration: Host, port, debug mode, etc.
- Consultant Configuration: Memory types, extraction prompts, etc.
License
This project is licensed under the MIT License - see the LICENSE file for details.