ima-mcp
Related Servers
Alternatives to ima-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that exposes Tencent IMA knowledge base capabilities, enabling RAG-based Q&A, file retrieval, note management, and web import through natural language.105MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for WizNote private server, enabling agents to search, read, write, and manage notes, and save webpages (including WeChat articles) as notes with image localization.1MIT
- AlicenseNot gradedqualityCmaintenanceA knowledge base MCP server that manages notes with digestion and excretion features, supporting search, read, and stats tools.MIT
- FlicenseAqualityBmaintenanceA local MCP server for managing Markdown notes, enabling create, list, read, search, summarize, and delete operations through natural language.61-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to search, read, and create notes across six note-taking platforms (Feishu, Obsidian, Notion, Yuque, OneNote, Evernote) through a single unified interface.MIT
- AlicenseNot gradedqualityCmaintenanceA learning-oriented MCP server for managing notes, providing tools to create, list, get, update, delete, and search notes, along with resources and prompt templates.5 npmMIT
TDQS
Scored across 19 tools
Most tools map to distinct resource+action pairs, but two pairs blur: ima_append_note vs ima_insert_images_to_note (which also appends Markdown, just with images) and ima_search_knowledge_bases vs ima_get_addable_knowledge_bases vs ima_get_knowledge_base, which are all 'get knowledge base' variants differentiated mainly by description prose. Similarly ima_list_knowledge vs ima_search_knowledge and ima_check_repeated_names vs ima_upload_file_to_knowledge (upload does precheck+dedupe internally) overlap, so selection requires reading descriptions carefully.
All 19 tools use a consistent ima_ prefix with snake_case verb_noun structure, which is predictable. Minor deviations exist: some verbs are compound (ima_insert_images_to_note, ima_get_addable_knowledge_bases) and ima_raw_call is not a verb_noun resource action, but overall the convention holds.
19 tools is on the heavy side for a notes/knowledge-base integration, and several are thin helpers (ima_check_repeated_names, ima_get_image_url, ima_raw_call) that exist mainly to work around API constraints. Each does earn a place, but the surface is broader than necessary for the core note+KB workflows.
Read/create/append coverage for notes and KBs is solid, and import/upload/media paths are covered. However obvious lifecycle operations are absent: no update/rename/delete note, no create/delete notebook, and no delete/remove-from-knowledge-base tool, leaving agents at dead ends for maintenance tasks (ima_raw_call is only a workaround).