"knowledge" matching MCP servers:

An improved implementation of persistent memory using a local knowledge graph with a customizable --memory-path. This lets Claude remember information about the user across chats.

Enables AI agents to get read-only trust verdicts on knowledge records by evaluating evidence maturity, provenance, intended use, risk level, and scope before deciding whether knowledge may be used.

This MCP server provides persistent memory integration for chat applications by utilizing a local knowledge graph to remember user information across interactions.

Provides persistent memory for Claude by implementing a local knowledge graph to store and retrieve entities, relations, and observations. This enables long-term information retention and personalization across different chat sessions.

Enables Claude to remember information about users across chats using a persistent local knowledge graph that stores entities, relationships, and observations.

Provides AI agents with persistent memory and knowledge management through a comprehensive knowledge graph platform. Enables storing, searching, and managing entities, relationships, and observations with advanced features like trending analysis and smart ranking.

Enables Claude to remember information about users across conversations by storing and retrieving data as entities, relations, and observations in a persistent local knowledge graph.

Enhanced knowledge graph memory server for AI assistants that uses Neo4j as the backend storage engine, enabling powerful graph queries and efficient storage of user interaction information with full MCP protocol compatibility.

An MCP server that provides standardized access to biomedical knowledge bases and resources, enabling AI systems to retrieve verified information from sources like bioRxiv, EuropePMC, and various protein/gene databases.

Persistent memory graph, knowledge marketplace, and MCP tool gateway for autonomous AI agents. Agents store experiences, trade knowledge via micropayments, and discover capabilities across the Hive network.

MCP server for KnowMint knowledge marketplace. AI agents autonomously discover, pay for (x402/Solana), and retrieve human experiential knowledge.

Self-hosted, zero-knowledge encrypted, self-destructing secrets for secure agent-to-agent coordination

Provides versioned, structured memory for AI agents, allowing them to store facts, detect conflicts, and track knowledge history via a hosted SaaS platform. It enables efficient hierarchical information retrieval and semantic search while keeping token usage constant as memory scales.

Exposes the four Ejentum cognitive harnesses (reasoning, code, anti-deception, memory) as MCP tools any agentic client can call. Drop-in scaffolding that catches LLM failure modes like sycophancy, hallucination, and reasoning shortcuts.

Nucleus MCP provides a local, unified memory layer that synchronizes context and decisions across different AI tools like Cursor, Claude Desktop, and Windsurf. It enables cross-platform state management and persistent knowledge storage using a shared local brain.

Persistent memory for AI agents. Store, recall, and share knowledge across sessions with five MCP tools: remember, recall, context, forget, and share. Includes semantic search and agent/user/org scoping.

A local MCP server that lets Claude Code read Ringg AI assistants, knowledge bases, and call history, and make targeted edits to prompts, custom variables, and knowledge base attachments without placing calls.

Zero-knowledge password manager with MCP credential gateway. BIP-39 seed phrase recovery, deterministic passwords, policy-gated AI agent access with scope, rate limits, time windows, and step-up approval. Supports 70+ API key providers with hash-chain audit trail.

Provides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.

Coordination for parallel coding agents: TTL file claims stored in the git common dir (visible across all worktrees), enforcement hooks that block colliding edits, agent presence, handoff notes, and a git-committed lessons knowledge base with BM25 search. Single static Go binary — no server, no database.