istefox-dt-mcp
OfficialRelated Servers
Alternatives to istefox-dt-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive management of DEVONthink records and databases, including searching, creating, and modifying content via JXA. It also integrates bibliography metadata resolution to link DEVONthink attachments with Zotero-exported citation data.4-
- FlicenseBqualityAmaintenanceEnables local, offline document extraction and manipulation—PDF first but also HTML, DOCX, XLSX, PPTX, EML, EPUB, Markdown, and plain text—through tools for probing, locating, extracting, converting, assembling, OCR, protecting, and redacting documents, with nothing leaving the machine.7-
- FlicenseBqualityBmaintenanceProvides 32 local tools for managing briefs, dispatch, run events, registry, and redaction in AI-assisted workflows, operating entirely on local markdown/JSON files with no network calls.32-
- AlicenseAqualityCmaintenanceDescription: Persistent memory for AI agents with rollback, audit trails, semantic search, and knowledge graph. Zero-config local SQLite or cloud API. 23 tools, 6 resources, 3 prompts.235 npm1MIT
- AlicenseNot gradedqualityAmaintenanceProvides 11 MCP tools for deterministic, local semantic search over your documents, including indexing, retrieval, exact-match facets, temporal truth, semantic diff, and agent-first JSON output. Enables LLMs and agents to search, retrieve, and analyze documents without cloud dependencies or per-query costs.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceA database-first personal knowledge management system powered by a local MCP server, providing 29 tools to manage and search structured knowledge (meetings, emails, people, accounts, projects, todos, etc.) via a single SQLite file.-
TDQS
Scored across 7 tools
Multiple tools appear to overlap in purpose, such as 'search', 'find_related', and 'ask_database', which all seem to query data in some form. Without descriptions, an agent would struggle to differentiate these, leading to potential misselection. 'file_document' and 'bulk_apply' are also vague and could be interpreted in multiple ways.
All tool names use snake_case and mostly follow a verb_noun pattern (list_databases, find_related, summarize_topic), but the verbs themselves are inconsistent, mixing generic actions like 'search' and 'ask' with more specific ones. This creates a somewhat readable but not fully predictable naming scheme.
With 7 tools, the server is well within the ideal 3-15 range for a focused utility. Each tool seems to cover a distinct (if overlapping) aspect of data interaction, and the count is neither thin nor bloated.
The tool surface lacks clear lifecycle coverage for any specific resource. There is list and search functionality, but no obvious create, update, or delete operations for databases or documents, making the server feel like a partial toolkit. The domain itself is ambiguous, so it is unclear what the intended complete workflow would be.