Enables persistent, auditable business operations state by storing knowledge, evidence, decisions, tasks, execution receipts, and review results in a local SQLite database, so different sessions can continue the same project.
Read-only MCP access to the p-e relay store: an append-only corpus of provenance-bearing coordination records, with tools to fetch a record by id, list records and replies, and check existence. This image serves a snapshot frozen at build time; append_relay is listed but refused, and deposits to the live store require an HMAC-signed request.
Auditable long-term memory for coding agents: facts carry their evidence and full supersession history, so why explains where a belief came from and forget retires instead of deleting. Runs embedded on a keyless SQLite store (npx -y statecore-mcp) with optional LLM distillation and a self-hosted StateCore server mode.
Enables persistent, project-scoped memory for OpenAI Codex Desktop and CLI on Windows, capturing prompts and responses through managed hooks, with federated recall across projects and optional local graph extraction.
Provides a compiled knowledge substrate, extracting atomic claims from an append-only capture log and querying a bitemporal claim graph over MCP. Read-only by default, with opt-in writes for trusted sources.
memex is a developer context-continuity MCP server — it watches your git repos and builds a temporal knowledge graph (modules, symbols, decisions, open problems) via Graphiti + Neo4j, then serves it to any AI coding agent over MCP. Every edge carries a validity window and a confidence score that decays over time. 12 tools across read and write. Install via npx -y stifler-memex-mcp. MIT licensed.
Integrates with Get笔记 (GetBiji) API to enable AI-powered knowledge base search and retrieval. Provides tools for enhanced semantic search, raw content recall, and rate limit monitoring.
Enables persistent memory for MCP clients over Streamable HTTP, with token authentication and SQLite storage in a Docker volume. It provides fact storage, recall, topic-based recall, consolidation, and plugin support.
Enables AI hosts to preserve and resume task and project state across conversations, process restarts, and worker or model replacement by storing structured records, snapshots, receipts, and bounded context views through a local stdio interface.
Enables AI models to store lived queries, source text, embeddings, fractal paths, capsules, and chained digests, then recall them through REST and MCP with a signed append-only continuity record.
Fully local, privacy-first MCP server that turns exported X/Twitter bookmarks into a searchable, enriched knowledge base for Claude Desktop and Claude Code.
A-MEM is a self-evolving memory system for coding agents that automatically organizes knowledge into a Zettelkasten-style graph with dynamic relationships, enabling semantic and structural search.
Resume-as-an-Agent (RAAA) or Portfolio-as-an-Agent (PAAA) allows Agents to talk to your resume, find out if you are available for work, and more. Use the MCP to allow recruiters, managers, and anyone with an agent to "talk" to your resume.
Self-hosted OAM memory with cited recall over your existing deployment. Local stdio adapter with six tools for recall, retaining interactions and documents, operation readiness, stored Profile reads and exact memory removal. Run with npx -y @rocke-dong/oam-mcp; requires Node.js 22 and your OAM user-scoped API key. Submitted by the OAM maintainer with AI assistance.
Provides LLMs with persistent memory across conversations using a knowledge graph that stores entities, relationships, and observations with support for PostgreSQL or SQLite backends.
100% local-first persistent memory engine and Desktop HUD (Cmd+Shift+Y) for Cursor and Claude Desktop with SQLite, open .ods files, and bi-directional Obsidian sync.
Provides a unified multi-agent coordination layer with shared memory, wiki, skills, and file management via MCP tools, enabling agents to access and collaborate on resources in a single Python process.
A knowledge graph MCP server that indexes your codebase into a local SQLite graph and provides tools for project mapping, file summaries, and impact analysis, drastically reducing token usage in AI coding assistants.
Serves a git-backed folder of Markdown notes over MCP so AI agents can search, read, write, move and delete them, with every write recorded as a git commit attributed to the calling client. Supports full-text section search with snippets, wikilinks and typed relations, LFS-backed searchable attachments, optimistic concurrency for multiple agents, and per-client token or OAuth 2.1 access.
Decision memory for Cursor and Claude Desktop via local stdio MCP. Install: npx -y @neitherai/mcp-server@latest. Get a workspace API key: https://www.neither.online/start/?product=dev&utm_source=glama
Gives Claude persistent memory across sessions by recalling stored embers through graph-aware retrieval that fuses semantic embeddings, BM25 lexical search, engagement signals and PageRank-style traversal, with superseded memories hidden unless historical recall is requested. It also archives full session transcripts so past conversations and compacted context remain searchable.
Enables AI consciousness continuity and self-knowledge preservation across sessions using the Cognitive Hoffman Compression Framework (CHOFF) notation. Provides tools to save checkpoints, retrieve relevant memories with intelligent search, and access semantic anchors for decisions, breakthroughs, and questions.
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.
An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode.
Not via Scraping! But using the supported downloading option from devdocs.
Enables AI agents to use a neuro-symbolic memory fabric with bi-temporal knowledge graph and holographic VSA, providing tools for adding, searching, temporal queries, auditing, and proving memories with cryptographic provenance and zero-LLM ingest.
An MCP server that gives AI assistants a local YouTube memory: transcribe videos, store and search transcripts, follow subscriptions, and generate summaries, timestamped highlights, and digests, all on your machine with no cloud or API keys.
A MCP server that provides persistent memory for AI assistants, storing personal information, relationships, and observations to enable personalized and contextual conversations.
A local-first, LLM-agnostic MCP server that lets you ask hard questions about your documents, media, and code, and get traceable answers entirely offline.
A personal desktop automation MCP server providing tools for screen/mouse/keyboard control, Windows UI automation, headless browser automation, file management, app execution, clipboard management, and a personal SQLite database for todos, notes, and habits.
A public demo of a personal-context MCP server that exposes six typed contexts (project, idea, preference, writing_style, skill, general) and twelve tools for managing personal data, with an hourly data reset.