Skip to main content
Glama

KnowS MCP Server

KnowS 医学证据检索与分析平台的 MCP (Model Context Protocol) Server。

安装与使用

前置条件

本包发布在 GitHub Packages,需要先配置 npm registry。在 ~/.npmrc 中添加:

//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN
@PancrePal-xiaoyibao:registry=https://npm.pkg.github.com

YOUR_GITHUB_TOKEN 需要有 read:packages 权限。

环境变量

变量

必填

说明

KNOWS_API_KEY

是

KnowS API 密钥

KNOWS_API_HOST

否

API 地址,默认 https://dev-api.nullht.com

Claude Code 配置

在 ~/.claude/settings.json 或项目 .claude/settings.json 中添加:

{
  "mcpServers": {
    "knows": {
      "command": "npx",
      "args": ["@PancrePal-xiaoyibao/knows-mcp-server"],
      "env": {
        "KNOWS_API_KEY": "your_api_key",
        "KNOWS_API_HOST": "https://api.nullht.com"
      }
    }
  }
}

Claude Desktop 配置

在 ~/Library/Application Support/Claude/claude_desktop_config.json(macOS)中添加:

{
  "mcpServers": {
    "knows": {
      "command": "npx",
      "args": ["@PancrePal-xiaoyibao/knows-mcp-server"],
      "env": {
        "KNOWS_API_KEY": "your_api_key",
        "KNOWS_API_HOST": "https://api.nullht.com"
      }
    }
  }
}

直接运行

# 通过 npx
KNOWS_API_KEY=your_key npx @PancrePal-xiaoyibao/knows-mcp-server

# 或全局安装后运行
npm install -g @PancrePal-xiaoyibao/knows-mcp-server
KNOWS_API_KEY=your_key knows-mcp-server

Related MCP server: Agent Care MCP

本地开发

# 安装依赖
npm install

# 使用 bun 开发(热重载)
KNOWS_API_KEY=your_key bun run dev

# 构建
npm run build

# 运行构建产物
KNOWS_API_KEY=your_key npm start

工具列表

工具

说明

ai_search

AI 检索,根据问题返回相关医学证据列表

evidence_summary

单篇证据 AI 概要总结

all_evidence_summary

获取所有证据的 AI 总结

evidence_highlight

获取证据被引用的原文内容

answer

基于问题和证据生成场景总结

answer_stream

场景总结(流式收集)

auto_tagging

证据自动化标签提取

get_paper_en

英文文献详情

get_paper_cn

中文文献详情

get_guide

指南详情

get_meeting

会议详情

list_questions

历史提问列表

list_interpretations

文献解读历史列表

create_evidence_by_pdf

通过 PDF 创建新证据

系统提示词

项目附带了推荐的系统提示词 SYSTEM_PROMPT.md,用于指导 AI 助手基于 KnowS 工具进行结构化的医学文献调研。

发版

# 更新 package.json 中的 version 后
git tag v0.x.x
git push origin v0.x.x

推送 v* tag 后,GitHub Actions 会自动运行测试并发布到 GitHub Packages。

Available Tools

14 tools
all_evidence_summaryA

获取所有证据的单篇 AI 总结(收集完整的流式响应后返回)

Inputs: no named parameters.

answerB

基于问题和检索出来的证据,生成场景总结(非流式)

Inputs: question_id (required), answer_type (required).

answer_streamC

基于问题和检索出来的证据,生成场景总结(收集完整的流式响应后返回)

Inputs: question_id (required), answer_type (required).

auto_taggingC

对证据进行自动化标签提取(如研究类型、疾病领域、样本量等)

Inputs: tagging_type (required), content, evidence_id.

create_evidence_by_pdfB

通过上传 PDF 文件创建新的证据

Inputs: pdf_base64 (required).

evidence_highlightB

返回单篇证据被引用的原文部分(高亮内容)

Inputs: evidence_id (required).

evidence_summaryB

对单篇证据进行 AI 概要总结

Inputs: evidence_id (required).

get_guideC

获取医学指南的详细信息

Inputs: evidence_id (required), translate_to_chinese.

get_meetingC

获取医学会议记录的详细信息

Inputs: evidence_id (required), translate_to_chinese.

get_paper_cnC

获取中文文献的详细信息

Inputs: evidence_id (required).

get_paper_enA

获取英文文献的详细信息(标题、摘要、影响因子、分区等)

Inputs: evidence_id (required), translate_to_chinese.

list_interpretationsC

获取用户的单篇文献 AI 解读历史记录,支持时间范围和分页

Inputs: from_time, to_time, page, page_size.

list_questionsC

获取用户的历史提问列表,支持时间范围和分页

Inputs: from_time, to_time, page, page_size.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have distinct purposes (e.g., ai_search vs. answer vs. evidence_summary). However, answer and answer_stream are clearly variants of the same operation, and all_evidence_summary and evidence_summary overlap in scope, causing slight ambiguity.

    Naming Consistency3/5

    Naming patterns are mixed: some tools use verb_noun (get_guide, list_questions) while others use noun_verb or noun_noun (evidence_highlight, ai_search). The presence of answer and answer_stream as single verbs breaks the pattern, reducing consistency.

    Tool Count5/5

    With 14 tools covering search, summarization, evidence management, and history, the count feels well-scoped for a medical knowledge server. Each tool serves a clear role without unnecessary redundancy.

    Completeness3/5

    The tool set covers core workflows like searching, answering, and summarizing, but lacks update/delete operations for evidence and does not provide listing tools for guides or meetings, leaving notable gaps in lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables comprehensive medical research by querying and analyzing data across ClinicalTrials.gov, PubMed, and FDA databases with AI-enhanced cross-database insights, risk assessments, and competitive intelligence.
      13
      11
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Integrates with EMRs like Cerner and Epic via FHIR to retrieve patient data, and provides medical research tools (PubMed, clinical trials, FDA) for clinical analysis.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables privacy-first medical document analysis with multi-perspective AI review. Ingest documents, run consilium reviews, generate doctor letters, and search patient memory—all through natural language.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables medical care management by retrieving and synthesizing PubMed literature, drafting provider emails for user review, and supporting human-in-the-loop approvals.
      -