A
licenseA
qualityA
maintenance.FAF (Foundational AI-context Format) with 50+ tools - Only Persistent project context that integrates seamlessly with Claude Desktop workflows. Officially merged (#2759) Anthropic MCP server.
14
1,271 npm
23
MIT
mcp-context-card
by Wolfe-Jam
Related Servers
Alternatives to mcp-context-card
Related Servers
- AlicenseAqualityAmaintenanceMCP server for managing project memory in AGENTS.md. Allows agents to record and remove durable facts using save/forget tools.313 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides a file-first personal memory layer for AI agents, enabling them to store and retrieve memories as markdown files with an SQLite index. The MCP server offers read-only search by default, with optional write tools for manual memory addition and conflict resolution.3 npmMIT
- AlicenseAqualityBmaintenanceMCP server for local-first project memory, enabling AI agents to log, search, and retrieve structured project history, summaries, and per-file dossiers with client-specific configuration and diagnostics.151MIT
- AlicenseBqualityDmaintenanceAn all-in-one MCP server that enables AI agents with local system capabilities like filesystem navigation, command execution, desktop automation, and a continuity memory suite for persistent cross-session project context.37MIT
- AlicenseNot gradedqualityDmaintenanceAn agent-capable MCP server with terminal access, filesystem control, and persistent memory. It includes sandboxing, access control, activity logging, and a file-backed memory store for context across conversations.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides controlled read/write tools for managing local-first research memory in an Obsidian vault, enabling AI agents to maintain project context across sessions.5 npm1MIT
TDQS
A3.9/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have distinct resource+action targets (author/read/list AGENTS.md, remember/recall/forget facts, whoami vs list_context_sources). The clearest overlap is save_context_card vs render_context_card, both about the context card, though descriptions clarify one renders to HTML and one saves a file. whoami and list_context_sources also touch identity/discovery but remain distinguishable.
Naming Consistency3/5
Six tools follow a clean verb_noun snake_case pattern (author_agents_md, list_agents_md_sections, list_context_sources, read_agents_md, save_context_card, render_context_card). The remaining four (forget, recall, remember, whoami) break that pattern into bare verbs/nouns. Mixed conventions but still readable and unambiguous.
Tool Count5/5
Ten tools is well within the ideal 3-15 range and each maps to a distinct capability (AGENTS.md authoring/reading, memory CRUD, card rendering/saving, identity, discovery). No tool feels redundant or padded.
Completeness4/5
Memory lifecycle (remember/recall/forget, with remember handling in-place updates) and card rendering/saving are complete. AGENTS.md has author/read/list-sections but author_agents_md only drafts and never writes a file, leaving a minor gap in the AGENTS.md write path that a client must work around.
Maintenance
ActivityActive
ResponsivenessUnresponsive