ima-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMA_OPENAPI_APIKEY | Yes | IMA OpenAPI API key (alternatively stored in ~/.config/ima/api_key) | |
| IMA_OPENAPI_CLIENTID | Yes | IMA OpenAPI client ID (alternatively stored in ~/.config/ima/client_id) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ima_search_notesC | 搜索 IMA 笔记，可按标题或正文搜索。 |
| ima_list_notesB | 列出 IMA 笔记。folder_id 为空时列出全部笔记。 |
| ima_list_notebooksC | 列出 IMA 笔记本。 |
| ima_get_note_contentC | 获取 IMA 笔记内容。默认返回纯文本。 |
| ima_create_noteC | 用 Markdown 内容创建 IMA 笔记。 |
| ima_append_noteC | 向已有 IMA 笔记末尾追加 Markdown 内容。 |
| ima_insert_images_to_noteA | 向 IMA 笔记末尾追加 Markdown 内容，并自动把内容里引用的图片（本地路径、file://、http(s) URL 或 data URL）内嵌进笔记。图片仅支持 PNG/JPEG/WebP 且必须严格小于 3MiB；连续文本合并为一批，每张图片单独一批，按原顺序逐批追加，失败即停。dry_run 可预览分批。 |
| ima_get_image_urlA | 把本地图片（PNG/JPEG/WebP，严格小于 3MiB）上传为 IMA 临时文件，返回可访问的临时 download_url。 |
| ima_search_knowledge_basesC | 搜索或列出 IMA 知识库。query 为空时按接口返回默认列表。 |
| ima_get_addable_knowledge_basesC | 获取当前用户可添加内容的 IMA 知识库列表。 |
| ima_get_knowledge_baseC | 按知识库 ID 获取 IMA 知识库信息。 |
| ima_list_knowledgeC | 浏览 IMA 知识库内容，可传 folder_id 进入文件夹。 |
| ima_search_knowledgeC | 在指定 IMA 知识库中搜索内容。 |
| ima_import_urlsA | 将网页或微信公众号文章 URL 导入 IMA 知识库。不传 folder_id 时导入到知识库根目录（接口要求 folder_id 必填，根目录传 knowledge_base_id）。 |
| ima_get_media_infoC | 获取知识库媒体的原文访问地址或笔记扩展信息。 |
| ima_add_note_to_knowledgeC | 把已有 IMA 笔记关联添加到 IMA 知识库。 |
| ima_check_repeated_namesB | 上传文件前检查 IMA 知识库内是否有同名条目。 |
| ima_upload_file_to_knowledgeB | 上传本地文件到 IMA 知识库：预检、查重、创建媒体、COS 上传、添加知识。 |
| ima_raw_callC | 直接调用 IMA OpenAPI 相对路径，用于未封装的新接口。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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).