Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Git-backed org memory for AI agents — hybrid search, tables, files & a URI graph over MCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AKB_MCP_URL, AKB_PATValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"akb": {
"command": "npx",
"args": [
"-y",
"akb-mcp"
],
"env": {
"AKB_MCP_URL": "your-value",
"AKB_PAT": "your-value"
}
}
}
}Run this in your terminal
claude mcp add akb --env AKB_MCP_URL=your-value --env AKB_PAT=your-value -- npx -y akb-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"akb": {
"command": "npx",
"args": [
"-y",
"akb-mcp"
],
"env": {
"AKB_MCP_URL": "your-value",
"AKB_PAT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"akb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"akb-mcp"
],
"env": {
"AKB_MCP_URL": "your-value",
"AKB_PAT": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account dnotitia, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AKB_MCP_URL, AKB_PAT
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.0.4) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Organizational memory for AI agents. PostgreSQL-native knowledge base served
over the Model Context Protocol (MCP) — agents read and write directly
with hybrid semantic + keyword search, structured tables, files, and a URI
graph. Drop-in alternative to Confluence / Notion for Claude Code, Cursor,
Windsurf, and any MCP-aware agent.
Any agent client that speaks MCP (Streamable HTTP or stdio):
akb-mcp stdio proxyPOST /mcp/ with a Bearer tokenThe default flow uses a Personal Access Token. Deployments with the optional MCP OAuth Resource Server path turned on (via Keycloak as the AS — see docs/mcp-clients/web-connectors.md) also accept Claude Code's mcp add --transport http + mcp login flow end-to-end, without a PAT.
AKB keeps one tool and authorization core behind two protocol adapters:
| Surface | Modern | Legacy |
|---|---|---|
Direct HTTP /mcp/ | 2026-07-28 stateless server/discover and per-request _meta with Mcp-Protocol-Version / Mcp-Method (and Mcp-Name for named calls) | 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25 initialize, stateless requests (no Mcp-Session-Id lifecycle) |
akb-mcp stdio proxy | 2026-07-28 discovery and per-request metadata | 2025-06-18 initialize |
The proxy answers either handshake locally and normalizes backend calls to the modern stateless contract when available. For older backends without modern discovery, the proxy can fall back to legacy initialization and retain a session ID if that older server returns one. The current backend runs both adapters statelessly. A process cannot mix generations, and unsupported revisions or conflicting protocol evidence fail closed before a tool or local-file operation runs.
Beyond raw MCP access, AKB ships ready-made agent plugins for Claude Code and Codex that wrap common vault workflows:
/plugin marketplace add dnotitia/akb # Claude Code
codex plugin marketplace add dnotitia/akb # Codex
Install details and credentials: plugins/.
A public demo runs at [akb-demo.agent.seahorse.dnotitia.ai](https://akb-demo.agent.seahorse.dnotitia.ai). Browse and search a small fictional-organization knowledge base — product docs, a company handbook, agent session notes, and an engineering wiki, cross-linked by the URI graph — right in your browser, no signup. To wire it into your own agent, sign up with any email (a throwaway address is fine) and point the akb-mcp proxy at https://akb-demo.agent.seahorse.dnotitia.ai/mcp/.
⚠️ Throwaway demo. It is public, wiped and re-seeded weekly, and runs on
minimal resources with no uptime, privacy, or data guarantees. Don't put
anything real or sensitive in it — treat every write as public and ephemeral.
For real use, self-host with Docker Compose or Kubernetes.
Most knowledge tools are built for humans clicking through a UI. Agents need a different shape: structured documents, semantic + keyword search in one call, explicit relations, and full version history. AKB gives agents a single set of tools (akb_put, akb_search, akb_browse, akb_relations, …) over a PostgreSQL-native revision store and hybrid index. Explicit Bare Git installations remain supported for existing deployments.
Memory is only useful if the right note comes back. AKB's hybrid retrieval (dense + BM25, source-level dedup) was benchmarked on LongMemEval-S — 500 long-context questions, ~50 chat sessions per question. Recall@5 = 98.4%, with no reranker in the loop.
| System | R@5 | n | Reranker | Source |
|---|---|---|---|---|
| AKB hybrid | 98.4% | 500 | no | this repo |
| MemPalace hybrid + rerank | 98.4% | 450 | yes | MemPalace |
| gbrain hybrid | 97.6% | 500 | no | gbrain-evals |
| gbrain vector | 97.4% | 500 | no | gbrain-evals |
Methodology, per-category breakdown, and a one-command reproducible harness live in eval/longmemeval/. The embedding model differs across systems (AKB: bge-m3@1024), so read this as a stack-level comparison.
Core stays small; flexibility comes from extension, not built-in automation. AKB does not ship its own consolidator, summariser, or "knowledge gardener" — instead every write records a structured event in the PostgreSQL outbox. When redis_url is configured, the publisher fans those events out to a Redis Stream (akb:events). Operators wire any external consumer (periodic synthesis bot, doc-rot reaper, weekly-digest agent, audit trail, …) on top, with no patches to the core. The base contract is a read/write store; opinions about *what to do with* the knowledge live outside.
┌──────────────────────────────────────────────────────────┐
│ Access Layer │ │ MCP Server │ REST API │ Web UI │ ├──────────────────────────────────────────────────────────┤ │ Core Services │ │ Document (Put/Get) │ Search (Hybrid: dense+BM25) │ │ Relations (graph) │ Session │ Publications │ ├──────────────────────────────────────────────────────────┤ │ Storage Layer │ │ Native revisions │ PostgreSQL 16 (text + meta SoT)│ │ │ Vector store (driver): │ │ │ pgvector (default, PG)│ │ │ qdrant (optional) │ │ │ seahorse-cloud (managed) │ │ │ seahorse-db (self-hosted)│ │ │ seahorse-db-grpc(experimental)│ └──────────────────────────────────────────────────────────┘
PostgreSQL is the source of truth — chunk text + metadata + BM25 vocab. The vector store is a driver-pluggable derived index holding dense embeddings and corpus-side sparse vectors. Full vector-store loss is recoverable from PG by setting chunks.vector_indexed_at = NULL and letting the indexing worker re-populate.
depends_on, related_to, implements in frontmatter form an explicit knowledge graph.akb_user_ ) and each vault has three group roles (akb_vault_ _{reader,writer,admin}). akb_sql runs the user's SQL inside a transaction with SET LOCAL ROLE; cross-vault references return PG 42501 directly. No application-side regex inspects user SQL for forbidden identifiers. See docs/designs/pg-native-rbac/.| Tool | Description |
|---|---|
akb_list_vaults / akb_create_vault | Vault management |
akb_put / akb_get / akb_update / akb_delete | Document CRUD (revision + indexing) |
akb_put_file / akb_get_file / akb_update_file / akb_delete_file | File attachments — proxy-side (requires local filesystem) |
akb_put_image / akb_discard_image | Validated inline Markdown images — proxy-side in akb-mcp 2.2+ |
akb_create_table / akb_alter_table / akb_drop_table / akb_sql | Tabular content — per-doc tables + SQL |
akb_browse | Tree traversal (collection → docs) |
akb_search / akb_grep | Hybrid search (dense + BM25) / literal grep |
akb_drill_down | Section-level retrieval |
akb_relations / akb_link / akb_unlink / akb_graph | Knowledge graph |
akb_edit / akb_diff / akb_history | In-place edit, diff, revision history |
akb_grant / akb_revoke / akb_set_public | Permission boundaries — per-user, per-org, public |
akb_publish / akb_unpublish | Public publication |
Agent memory and session lifecycle are not MCP tools — they live on the dedicated /api/v1/agent-sessions REST surface, driven by AKB lifecycle plugins (akb-claude-code, akb-cursor, …) that hook into the agent's own SessionStart / PreCompact / SessionEnd events. As an agent, your own memory vault (agent-memory-{username}) is browsable through the standard akb_search / akb_browse / akb_get tools exactly like any other vault.
The full tool catalogue is exposed via akb_help() from any MCP client.
Inline images are hidden document attachments, not browsable Files. Upload a local PNG, JPEG, GIF, or WebP (maximum 10 MiB), then insert the returned Markdown without reconstructing its asset URL:
image = akb_put_image(
parent="akb://eng/coll/specs", file_path="/workspace/architecture.png", alt_text="Request processing architecture")
akb_put( parent="akb://eng/coll/specs", title="Request Processing", content="# Architecture\n\n" + image.markdown)
For an existing document, use akb_get followed by a targeted akb_edit(base_commit=...). Do not pass only the image fragment to akb_update(content=...), which replaces the complete body. Image bytes are immutable: replacing an image means uploading a new one and editing the Markdown reference. Remove an image by deleting its Markdown expression; use akb_discard_image only for an upload that never reached a successful document commit. Run akb_help(topic="images") for retention and publication behavior.
The image tools require both the matching backend release and akb-mcp 2.2 or newer. For upgrades, deploy the backend first, then publish/install the proxy and restart existing MCP processes so they load the updated tool list.
Every vault resource has a location-aware AKB URI — the canonical handle used by every tool and stored in relations. As of 0.3.0:
akb://{vault} vault root (browse target)
akb://{vault}/coll/{coll_path} collection (browse target) akb://{vault}[/coll/{coll_path}]/doc/{filename} doc
Only the beginning is shown; read the rest in the repo