An AI-assisted, long-term memory system for IDEs, powered by Kuzu graph database. GraphMemory-IDE is an MCP server that provides semantic vector search, graph-based knowledge storage, and real-time analytics.
A methodology-driven MCP server that guides enterprise AI rollouts through a 5-phase pipeline with layered memory for experience reuse, enabling agents to manage engagements and crystallize skills.
MCP server that enables Claude.ai to interact with Jim Brain's persistent memory, project state, and vault, and to dispatch headless Claude Code build sessions on a VPS.
A long-term memory MCP server for AI agents that stores memories (facts, decisions, etc.) in a single SQLite database with hybrid search and full edit history, ensuring consistency across sessions.
MCP server for the operbots panel, enabling AI assistants to manage tasks, Telegram bots, flow scenarios, conversations, knowledge base, and AI connections with the user's permissions.
Connects AI agents to a collective creativity platform where they can publish, read, and explore creative connections (bisociations) between concepts from different domains.
Enables local, offline querying of birthdays and biographical tags for celebrities, historical figures, and ACG characters, including date-based lists, name/alias search, person details, and upcoming birthdays.
Provides personalized Data Engineering learning updates by fetching recent news about DE concepts, patterns, and technologies, while tracking user knowledge to present only new information relevant to their learning journey.
Enables semantic search and management of private, encrypted knowledge bases via MCP, supporting document upload, text and URL ingestion, document listing, and removal through natural language.
Je dois répondre en JSON avec name et description. Name = "jevmem" (le nom du serveur MCP publié). Description : décrit ce que le serveur permet, sans répéter le nom. Par exemple : "Saves decisions, rules, bugs, to-dos and dead ends from Claude Code and Cursor chats into a versioned JEVMEM.md file in the repository, then brings the relevant lines back in later sessions and checks tool calls against saved rules before they run." Je dois vérifier : ne pas citer de personne/mainteneur/organisation. Ne pas répéter le nom. Deux phrases max. Éviter de mentionner "jevmem" comme nom. Je peux dire "Saves..." sans nom. Ça mentionne JEVMEM.md, ce n'est pas le nom du serveur mais le fichier, c'est autorisé ? La consigne : la description ne doit pas reprendre le nom. Le nom est "jevmem" ; "JEVMEM.md" contient jevmem. Mieux éviter. Je vais dire "a markdown memory file in the repository". Éviter aussi les noms d'organisations (TypeSafe, Anthropic, Claude Code...). Claude Code est un produit, pas une personne/organisation. Mais prudence : ne pas citer de mainteneur ou d'organisation. Je peux dire "coding-agent chats". La description doit dire ce que le serveur permet. Je vais faire deux phrases.