A
licenseA
qualityC
maintenanceEnables creating meeting minutes from unstructured meeting memos with validation, grounding checks, and user-approved saving.
11
MIT
asistonto-mcp
by R0DR0X
Related Servers
Alternatives to asistonto-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search meeting transcripts, retrieve speaker-attributed quotes, decisions, and action items, and transcribe new files or links directly from the QuillHub archive.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to save, search, read, update, and delete personal notes, summarize topics, and generate quizzes from saved notes through MCP tools, resources, and prompts.71MIT
note1 MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve meeting notes, summaries, and transcripts from note1, with tools to export markdown, check recording status, and manage meeting recordings.308 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read, search, create, edit, move, and version Markdown notes, folders, tags, tasks, and attachments. It also supports generating meeting reports and bulk-importing notes through authenticated MCP connections.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to programmatically create, validate, store, and hot-swap interactive quizzes and study bundles into a desktop learning application, with analytics and local REST integration.MIT
TDQS
A3.6/5.0
Scored across 9 tools
Disambiguation4/5
Most tools have clearly distinct purposes: parsing notes, composing questions, checking paraphrases, validating packs, rendering documents, and reading/writing packs all target different stages. The only minor overlap is between validate_pack and read_pack, since read_pack also validates, but the descriptions make the distinction clear.
Naming Consistency3/5
The majority of tools follow a verb_noun pattern (compose_question, parse_meeting_notes, validate_pack, write_pack, read_pack), but two exceptions break the convention: pack_authoring_guide and pack_size_floor are noun phrases with no verb. This mixed pattern is readable but not fully consistent.
Tool Count5/5
With 9 tools, the server is well-scoped for its purpose. Each tool covers a distinct step in the pack authoring workflow, and there is no obvious redundancy or bloat.
Completeness4/5
The tool set covers the full authoring lifecycle: guidance, parsing, composing, paraphrasing, validation, rendering, writing, reading, and sizing. Minor gaps exist (no explicit delete or update operation, no batch listing), but write_pack can overwrite packs and the core workflow is complete.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues