Src To Kb vs Agent Recall — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Src To Kb vs Agent Recall
In-depth architectural comparison of the Src To Kb and Agent Recall MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Src To Kb
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Agent Recall
Knowledge & Memory · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Src To Kb if you need specialized Knowledge & Memory tools running via a local process. Choose Agent Recall if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Src To Kb when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
Primary tools included: Multi-language source-code processing, Configurable code chunking and overlap, Optional comment removal and whitespace normalization.
Convert source code repositories into searchable knowledge bases with AI-powered search using GPT-5, intelligent chunking, and OpenAI embeddings for semantic code understanding.
Src To Kb is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agent Recall belongs to Knowledge & Memory using local stdio subprocess. Select Src To Kb when you need capabilities focused on knowledge & memory and Agent Recall when you require tools for knowledge & memory.
[ENTRY — call FIRST, before acting] Use when the user asks to start, load, continue, resume, or open memory for a project. Set mode='lite' for a ≤500-token briefing (good for fresh conversations where the agent will pull memory on demand via recall()).
session_end
[ON SAVE/EXIT — YOU must call this; nothing auto-saves] Use when the user asks to save, checkpoint, summarize, end, retain, or persist the current session. Optionally pass close_phase / open_phase to update the project pipeline narrative spine in the same call.
remember
[MID-SESSION WRITE — single fact/decision; saying it is not saving it] Use when the user asks to remember, store, note, or save a specific decision, fact, or insight.
recall
[RETRIEVE — use freely, any time] Use when the user asks to recall, search, find, or look up previous memory, context, or decisions.
check
[MID-SESSION — safe any time; for alignment, before risky decisions] Use when the user asks to validate understanding, verify alignment, or check if their interpretation matches the human's intent. Also call BEFORE a high-risk action — publish, deploy, delete, credential exposure, external send/message, or any other irreversible write — passing `action_description` (one sentence, what you're about to do). Returns matching corrections/rules/insights plus a `verdict`: `blocked` means an authoritative correction OVERRIDES the plan — read it before proceeding. To RECORD a durable human correction, pass `human_correction` as the STRUCTURED object {rule, why, applies_when} — a plain string is only STAGED for later review, never activated.