mcp-context-card
Related Servers
Alternatives to mcp-context-card
- AlicenseAqualityBmaintenance.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.14529 npm23MIT
Related Servers
- AlicenseAqualityAmaintenanceMCP server for managing project memory in AGENTS.md. Allows agents to record and remove durable facts using save/forget tools.3497 npm1MIT
- AlicenseNot gradedqualityBmaintenanceProvides 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.2 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
- FlicenseBqualityCmaintenanceAn 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.37-
- 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.9 npm1MIT
TDQS
Scored across 10 tools
Most tools target clearly distinct resources and actions: AGENTS.md listing/reading/authoring, memory create/read/delete, identity, discovery, and card rendering/saving. The only mild overlap is between render_context_card and save_context_card, and between whoami and list_context_sources, but the descriptions distinguish them well.
The set is mostly consistent verb_noun snake_case (list_agents_md_sections, read_agents_md, author_agents_md, list_context_sources, render_context_card, save_context_card). The memory tools use simple verbs (remember, recall, forget) and whoami is a special-case command, which are minor deviations but still readable.
Ten tools is well-scoped for a context-card server covering AGENTS.md, memory, identity, discovery, and rendering. Each tool earns its place and there is no evident bloat.
Core lifecycle operations are present: AGENTS.md can be listed, read, and drafted; memory can be created, recalled, and forgotten; identity, discovery, and card rendering/saving are covered. Minor gaps exist, such as no explicit listing of all stored memory facts and no direct write of AGENTS.md, but agents can work around these with known IDs or external file writes.