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
note1 MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables 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.8 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Google NotebookLM notebooks, add sources from URLs, YouTube, Drive, or text, query and summarize content, and generate audio overviews, infographics, and slide decks through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to save and recall information from files or free-form notes using natural language, acting as a long-term memory system.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to programmatically create, manipulate, and analyze Microsoft PowerPoint presentations with advanced formatting and template management.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with OpenAPI documents for analysis, validation, and management through structured interfaces.301 npm3ISC
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
ActivityMaintained
ResponsivenessNo issues