MCP Context Card vs Shodh Memory
A side-by-side look at the MCP Context Card and Shodh Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Context Card for knowledge & memory work as a local process; choose Shodh Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Context Card when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
read_agents_md, author_agents_md, list_agents_md_sections.
Choose Shodh Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
remember, recall, recall_by_tags.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 64/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 322 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 10 | 38 |
| Full listing | View MCP Context Card | View Shodh Memory |
Tools & capabilities
MCP Context Card tools 10
read_agents_mdReturn this project's AGENTS.md — the whole file, or one section by heading. The instructions a client would otherwise have to know to look for and read wholesale.author_agents_mdAuthor an AGENTS.md for this project and return the draft — BETTER from repo facts alone (via agents-md-facts: real build/test commands, entry points, toolchain conventions, nothing invented), or BEST when a project.faf exists (facts plus its structured goal/who/why as a second managed block ahead of them). Does not write a file.list_agents_md_sectionsList the headings in this project's AGENTS.md, so a client can pull one section instead of spending context on the whole file.rememberPersist a fact past the session boundary — written to a .fafm file, not held in memory. Reusing an existing id replaces that fact's text in place (no duplicate); a new id appends. Facts are written verification_status: unverified.recallRetrieve a fact stored in a previous session by id. Exact lookup — not fuzzy or substring.forgetRemove a fact by id — to correct or drop something stale. A missing id is reported, not an error.whoamiThis server's own identity — name, vendor, version, status, license — from its .fafa card.list_context_sourcesWhat context does this project publish (AGENTS.md, memory, identity), in what media types, and through which discovery surface. For a client connecting cold.render_context_cardRender the project's business card as one self-contained HTML page a person can read or screenshot. Front: name, title, one-liner. Flip it for the back: About, Skills (when the .fafa lists any), Context (AGENTS.md), Memory, Discovery. layout:"portrait" for the tall view; expanded:true renders both faces flat with every section open. Also served at GET /card (?expand=all) over the HTTP transport.save_context_cardWrite the context card to context-card.html in the project and, when this server runs locally, open it in the person's browser. Returns the card as Markdown (identity, AGENTS.md sections, memory, discovery) plus a clickable link to the saved file. Use this instead of pasting render_context_card's HTML into a chat that can't display it. Replaces any earlier context-card.html.
Shodh Memory tools 38
rememberStore a memory for future recall. Use this to remember important information, decisions, user preferences, project context, or anything you want to recall later.recallSearch memories AND todos using semantic similarity. Returns both relevant memories and matching todos. Use this to find past experiences, decisions, context, or pending work. Modes: 'semantic' (vector similarity), 'associative' (graph traversal), 'temporal' (time-based retrieval), 'hybrid' (combined), 'spatial' (geo-location based), 'mission' (mission context), 'action_outcome' (reward-based learning).recall_by_tagsFind memories by tags. Returns memories matching ANY of the provided tags. Useful for finding memories by category (e.g., 'tool:Edit', 'file:src/main.rs', 'source:hook', 'error', 'session-summary').context_summaryGet a condensed summary of recent learnings, decisions, and context. Use this at the start of a session to quickly understand what you've learned before.list_memoriesList all stored memoriesforgetDelete a specific memory by IDmemory_statsGet statistics about stored memoriesverify_indexVerify vector index integrity - diagnose orphaned memories that are stored but not searchable. Returns health status and count of orphaned memories.repair_indexRepair vector index by re-indexing orphaned memories. Use this when verify_index shows unhealthy status. Returns count of repaired memories.backup_createCreate a backup of all memories. Returns backup metadata including ID, size, and checksum. Backups are stored locally and can be restored later.backup_listList all available backups for this user. Returns backup history with IDs, timestamps, and sizes.backup_verifyVerify backup integrity using SHA-256 checksum. Use to check if a backup is corrupted before restoring.- +26 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Context Card
{
"mcpServers": {
"mcp-context-card": {
"command": "npx",
"args": [
"-y",
"mcp-context-card"
]
}
}
}
Shodh Memory
{
"mcpServers": {
"varun29ankus-shodh-memory": {
"command": "npx",
"args": [
"-y",
"@shodh/memory-mcp"
]
}
}
}
Frequently asked questions
MCP Context Card is categorized under Knowledge & Memory and uses a local stdio subprocess. Shodh Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Context Card for knowledge & memory work and Shodh Memory for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Context Card is listed as free. Auth: no auth required. Shodh Memory is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-context-card and varun29ankus-shodh-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Context Card has a quality signal of 64/100 (Good) with 0 views, 0 installs and 3 GitHub stars. Shodh Memory has 69/100 (Great) with 8 views, 0 installs and 322 GitHub stars.