Skip to main content
Glama
rowanlin-dev

ima-mcp-server

by rowanlin-dev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
IMA_API_KEYNoYour IMA API Key
IMA_CLIENT_IDNoYour IMA Client ID (obtained from https://ima.qq.com/agent-interface)
IMA_OPENAPI_APIKEYNoYour IMA API Key (compatible with ima-skill env var name)
IMA_OPENAPI_CLIENTIDNoYour IMA Client ID (compatible with ima-skill env var name)

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_knowledge_baseA

搜索知识库列表。query 传空字符串时返回当前账号下所有可见知识库(含自建与订阅)。知道知识库名称但不知道 ID 时用此接口。

get_knowledge_baseA

获取知识库详情(描述、推荐问题等)。支持一次查询 1-20 个知识库。

get_knowledge_listA

浏览知识库内容列表(根目录或指定文件夹),分页返回文件与子文件夹。操作根目录时省略 folder_id。folder_id 以 folder_ 前缀开头。

search_knowledgeA

在指定知识库中按关键词搜索内容(含文件和文件夹),返回命中的标题、摘要片段。这是知识库内容检索的核心接口。

get_media_infoA

获取知识库条目的原文内容或下载链接。传入 media_id(来自 get_knowledge_list 或 search_knowledge 的返回)。对微信文章/网页/文件类,返回可访问 URL;对笔记类(media_id 以 note_ 开头),会自动拉取并返回笔记正文(note_content 字段,纯文本)。

get_note_contentA

读取笔记正文(纯文本)。传入 note_id(笔记的数字 ID,即 get_media_info 返回的 notebook_id,或笔记搜索接口返回的 doc_id)。这是读取 IMA 笔记原文的专用接口。

get_addable_knowledge_base_listA

获取当前用户有权限添加内容的知识库列表。仅在未指定目标知识库时使用。

import_urlsA

将网页或微信文章 URL 添加到知识库(1-10 个 URL)。添加到根目录时省略 folder_id。

upload_fileA

将本地文件上传到指定知识库(支持 PDF / Word / PPT / Excel / Markdown / 图片 / TXT / XMind / 音频 / HTML 等)。内部流程:类型与大小预检 → 重名检测(命中自动追加时间戳)→ create_media 获取 COS 临时凭证 → 上传 COS → add_knowledge 正式入库。视频文件(.mp4 等)不支持,请改用 import_urls 以 URL 方式添加。verify=true 时仅上传到 COS 不入库,便于验证凭证与网络。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 9 tools

Disambiguation4/5

Most tools have distinct purposes (search vs list vs get, etc.), but get_media_info and get_note_content both handle note retrieval, and search_knowledge_base and get_knowledge_base both deal with KB metadata. Descriptions help clarify which to use, so confusion is limited.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_, search_, import_, upload_). The naming is uniform and predictable, with no mixed casing or irregular verb styles.

Tool Count5/5

9 tools is well within the ideal 3-15 range. Each tool serves a clear purpose in the knowledge base workflow, and the set feels neither bloated nor sparse.

Completeness4/5

The tool set covers the core workflow well: finding KBs, browsing content, searching, retrieving full content, and adding content via URL or file upload. Missing update/delete operations, but these may be outside the intended scope for this server.

Maintenance

ActivityMaintained
ResponsivenessSyncing