Agent Knowledge
Persist decisions, facts, and context in a scored knowledge graph the agent can search across sessions.
Overview
agent-knowledge is a MCP server for the Build phase that provides cross-session agent memory via a knowledge graph, scoring, and semantic search over stdio.
What is this MCP server?
- Cross-session memory with knowledge graph storage
- Scoring and semantic search over accumulated agent knowledge
- stdio npm package agent-knowledge at version 1.9.7
- Complements agent-comm and agent-discover in the same agent stack family
- GitHub source keshrath/agent-knowledge for local deployment
- Package version 1.9.7
- Transport: stdio
- Registry: npm identifier agent-knowledge
Community signal: 7 GitHub stars.
What problem does it solve?
Every new agent session forgets your project context, so you repeat explanations and rediscover the same solutions.
Who is it for?
Long-horizon solo projects where the coding agent must remember architecture, users, and prior debugging across weeks of work.
Skip if: Teams that need enterprise RAG with strict ACLs only, or workflows where ephemeral chats with no memory are preferred.
What do I get? / Deliverables
Facts and decisions persist in a searchable knowledge graph so later sessions retrieve relevant context semantically.
- Persistent knowledge graph accessible from the agent via MCP
- Semantic search and scored recall across sessions
- Less repeated context-setting at the start of each chat
Recommended MCP Servers
Journey fit
Long-lived agent memory is first installed while building your agent stack, then pays off across operate and support work. Agent-tooling is the shelf for memory, retrieval, and semantic search MCP servers that augment the coding agent.
How it compares
Agent memory graph MCP, not a hosted analytics warehouse or a single-shot brainstorming skill.
Common Questions / FAQ
Who is agent-knowledge for?
Indie builders running MCP agents on sustained codebases who want durable, searchable memory beyond one chat window.
When should I use agent-knowledge?
Use it when you start building with agents and expect to iterate for months, especially if you revisit the same domains in Operate and Support.
How do I add agent-knowledge to my agent?
Add npm package agent-knowledge (v1.9.7) with stdio transport per keshrath/agent-knowledge repository instructions.