Filigree
Related Servers
Alternatives to Filigree
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceProvides AI agents with durable, searchable project memory, session notes, skills, and bounded context packs over MCP while leaving orchestration to the client.15MIT
- FlicenseNot gradedqualityCmaintenanceShared project memory MCP server for storing and retrieving technical decisions, lessons learned, ADRs, and cross-links between projects.-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents and users to search a unified organizational knowledge warehouse, create and iterate on documents, manage folders and reviews, and curate shareable knowledge packs through any compatible MCP client.-
- AlicenseNot gradedqualityCmaintenanceEnables multiple MCP-compatible AI clients to share persistent, versioned project knowledge across sessions with conflict-safe updates, provenance, hybrid retrieval, stale-memory handling, and context-budgeted recall.MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.19MIT
- AlicenseNot gradedqualityCmaintenanceProvides enterprise knowledge management capabilities via MCP, enabling semantic search across the knowledge base, retrieval of full documents by ID, and search over enterprise project cases.MIT
TDQS
Scored across 5 tools
Each tool has a fairly distinct role: listing projects, folder-to-project lookup, lexical search, context handoff, and a write proposal. The main overlap risk is search_memory vs get_handoff, since both return project knowledge, but the descriptions differentiate query-driven search from bounded current context well enough.
Four of five tools follow a clean verb_noun pattern (list_projects, search_memory, get_handoff, propose_memory). project_for_folder deviates into a noun_for_noun lookup style, which is a minor but readable inconsistency.
Five tools is well-scoped for a project-memory server: two discovery tools, two retrieval tools, and one write path. Each tool earns its place with no filler.
The surface covers project discovery, memory search, context retrieval, and proposal submission, and explicitly documents what is out of scope (approval/publishing). Minor gaps remain: no tool to fetch a single memory entry by ID or to update/retract a proposal.