MCP Context Card vs Th Memory MCP
A side-by-side look at the MCP Context Card and Th Memory MCP 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 Th Memory MCP 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 Th Memory MCP 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 have the keys it needs:
MEMORY_DB_PATH. - You want tools like
remember, recall, get_profile.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 64/100 · Good | 64/100 · Good |
| 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 | MEMORY_DB_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 10 | 16 |
| Full listing | View MCP Context Card | View Th Memory MCP |
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.
Th Memory MCP tools 16
rememberSave or update a user preference (category+key upsert). Re-saving the same key increases confidence by 0.1 (cap 1.0). Returns the row id for forget().recallSearch preferences + lessons via full-text index, plus recent matching interactions. Use before starting a new task.get_profileGet the distilled user profile: profile sections, top preferences by confidence (max 15), and the 5 most recent lessons. Optional userId/sessionId/projectId scope the auto-projected memories; without them only GLOBAL memories are included.save_lessonRecord a lesson learned from a correction: what situation, what mistake, what is the correct way. Call immediately after the user corrects your work.search_historySearch past user prompts (kind='prompt') by keyword. Returns timestamped snippets truncated to 200 chars each.forgetDelete one memory row (preference, lesson or interaction) by id and sync the search index. Pass type when you know it (ids from remember are preference ids, from save_lesson are lesson ids).memory_statsSummarize memory usage: interaction counts by kind, preference/lesson totals, DB file size, oldest/newest interaction timestamps, and profile sections.get_recent_interactionsList recently captured raw interactions (newest first) as [id] ts [kind] content lines. Optionally filter by kind. Use for auditing history or before distilling memory.export_memoryExport preferences, lessons, profile (and optionally raw interactions) to a JSON file under data/exports/. Only writes inside that directory. Returns the file path, size in bytes and a JSON preview.get_contextAssemble relevant memories for the current task via hybrid retrieval (+ optional memory-graph expansion), with token budgeting. Use to load memory into context before a task.consolidateCluster similar memories via embedding similarity and optionally create derived/consolidated memories linked via 'derived_from'. Use during periodic consolidation.link_memoryCreate a typed relationship between two memories in the graph (supports/contradicts/supersedes/derived_from/related_to/caused_by/depends_on).- +4 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"
]
}
}
}
Th Memory MCP
{
"mcpServers": {
"th-memory-mcp": {
"command": "npx",
"args": [
"-y",
"th-memory-mcp"
],
"env": {
"MEMORY_DB_PATH": "YOUR_MEMORY_DB_PATH_HERE"
}
}
}
}
Frequently asked questions
MCP Context Card is categorized under Knowledge & Memory and uses a local stdio subprocess. Th Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Context Card for knowledge & memory work and Th Memory MCP 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. Th Memory MCP 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 th-memory-mcp 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. Th Memory MCP has 64/100 (Good) with 3 views, 0 installs and 3 GitHub stars.