F
licenseNot graded
qualityC
maintenanceEnables AI assistants to capture bookmarks, sticky notes, todos, notes, and web archives, and to search and organize personal knowledge and memory across cloud-synced clients.
-
Resurgo-MCP
Related Servers
Alternatives to Resurgo-MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenancePersonal knowledge graph with 16 MCP tools. Auto-links, deduplicates, tracks themes, synthesizes insights.178MIT
- AlicenseNot gradedqualityBmaintenanceEnables a local second brain for capturing notes, searching with AI-driven relevance ranking, and discovering connections between related pages, with persistent history and queue resumption.MIT
- AlicenseAqualityBmaintenanceBuilds a dynamic knowledge graph from your notes and uses LLM reasoning to discover blindspots, hidden cross-domain connections, track concept evolution, and spark creative inspiration.82Apache 2.0
- FlicenseBqualityDmaintenanceEnables indexing and retrieving notes with full-text search using SQLite, plus building knowledge graphs to find relationships between concepts. Supports natural language note management, tagging, and semantic connections.16-
- AlicenseNot gradedqualityAmaintenanceLocal markdown notes for any MCP client: ranked + semantic search, tags, todos, a wiki-link knowledge graph, daily notes, templates, and slash-command workflows. Pure-JS, local, no API keys.8 npm1MIT
TDQS
A3.5/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: complete_node marks nodes as done, get_due_items retrieves due items, quick_capture saves new nodes, search_nodes searches existing nodes, and snooze_node defers resurfacing. The descriptions make it easy to distinguish between creation (quick_capture), retrieval (get_due_items, search_nodes), and modification (complete_node, snooze_node) operations.
Naming Consistency5/5
All tools follow a consistent verb_noun naming pattern with snake_case: complete_node, get_due_items, quick_capture, search_nodes, and snooze_node. The verbs are clear and appropriate (complete, get, capture, search, snooze), and the nouns consistently refer to nodes or items, creating a predictable and readable set.
Tool Count5/5
With 5 tools, this server is well-scoped for managing nodes/items in a productivity or note-taking system. Each tool earns its place by covering core operations: capture (quick_capture), retrieval (get_due_items, search_nodes), and status updates (complete_node, snooze_node). The count is neither too thin nor bloated, fitting typical workflows efficiently.
Completeness4/5
The tool set provides strong coverage for a node management system, including creation, retrieval, and modification (completion and deferral). A minor gap exists in update operations for node content or metadata beyond scheduling, but agents can work around this by capturing new nodes. Core workflows like inbox review and search are well-supported, with no dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues