Zotero MCP 696200ee

MCP搜索检索

提供方 dengls24

搜索检索 未标注 无需鉴权 社区 / 第三方

An AI-powered research assistant that integrates with Zotero to read academic papers, create intelligent annotations, and generate structured notes. It enables users to highlight findings, explain formulas, and write comprehensive summaries directly within their Zotero library through natural language commands.

一句话选型结论

按资料字段整理

Zotero MCP 696200ee 属于搜索检索类 MCP 服务器,传输方式未标注,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类搜索检索 传输方式未标注 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

搜索检索
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

未标注 无需鉴权
上游未给出传输方式
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
联网搜索取证

让模型查最新资料并给出出处。

资料聚合

把一个主题的网页、文档集中抓回来整理。

情报与竞品检索

按关键词持续检索行业动态和竞品信息。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在搜索检索场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zotero MCP 696200ee当前 未标注 未标注 本地部署 无 2026-05-17
Brave Search 433812ff 2 未标注 未标注 无 2026-05-17
Sequentialthinking 1 SSE · 服务端推送 远程部署 有 2026-05-18
Baidu Netdisk 未标注 未标注 未标注 无 2026-05-17
ragflow 未标注 stdio · 本地进程 本地部署 有 2026-04-11
mindsdb (430e18) 未标注 未标注 未标注 有 2026-05-17

服务器档案

搜索检索
字段来自项目仓库与公开索引,中文说明由本站标注
提供方dengls24上游标注的维护方 dengls24
分类搜索检索本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

10.1 KB
来自项目仓库与上游目录的原文,未做删改

Annota — AI-Powered Paper Annotation Assistant

Turn your PDF library into an intelligent research assistant.

AI reads your papers, highlights key findings, explains formulas, and writes structured notes — all saved back to your reference manager.


What Can It Do?

You say... AI does...
"高亮摘要中的发现结果" (Highlight findings in the abstract) Reads the abstract, identifies findings, highlights them in green
"解释第3页的公式" (Explain the formulas on page 3) Extracts the formula, adds an explanation as a note annotation
"写一份结构化阅读笔记" (Write a structured reading note) Generates a note with contributions, methods, results, limitations — saved to your library
"以 MICRO 审稿人视角审阅" (Review as a MICRO reviewer) Produces a structured review with scores and actionable feedback

AI reads the paper → understands content → creates precise annotations

AI generates a structured reading summary with key findings, methods, and conclusions


✨ Features

9 MCP Tools

Tool What it does
search_zotero_items Search by title / author / key
list_zotero_items Browse recent items
get_item_metadata Get authors, year, venue, DOI
get_pdf_text_bulk Extract full text (no coords, fast)
get_pdf_layout_text Extract text + precise coordinates
list_annotations View existing annotations
create_pdf_annotation Create highlight / underline
batch_annotate Create multiple annotations at once
add_child_note Add a note to any item

3 Claude Code Skills (Slash Commands)

Command Function
/annota-annotate Smart annotation with semantic color coding
/annota-summarize Structured reading notes saved to your library
/annota-review Simulated peer review with scoring rubric

Smart Design

  • Two-phase workflow — Reads full text first (cheap), then only gets coordinates for target sentences (precise). Reduces context usage by 63–80%.
  • Auto-skip references — Detects "References" section and skips it. A 21-page paper extracts only 13 pages.
  • Batch annotations — Creates 10 highlights in 1 API call instead of 10.
  • Friendly errors — Write failures return helpful messages instead of crashing.

🚀 Quick Start (3 Minutes)

Step 1: Clone & Install```bash

git clone https://github.com/dengls24/annota.git
cd annota

python -m venv .venv

Windows:

.venv\Scripts\activate

macOS / Linux:

source .venv/bin/activate

pip install pymupdf mcp


### Step 2: Configure Claude Code

Add to `~/.claude.json` (or via Claude Code Settings > MCP Servers):

**Windows:**```json
{
  "mcpServers": {
    "annota": {
      "command": "C:/path/to/annota/.venv/Scripts/python.exe",
      "args": ["C:/path/to/annota/annota/server.py"],
      "env": {
        "ZOTERO_DATA_DIR": "C:/Users/YourName/Zotero"
      }
    }
  }
}

macOS / Linux:```json
{
"mcpServers": {
"annota": {
"command": "/path/to/annota/.venv/bin/python",
"args": ["/path/to/annota/annota/server.py"],
"env": {
"ZOTERO_DATA_DIR": "/Users/YourName/Zotero"
}
}
}
}


> **Finding your Zotero data directory:**
> - **Windows**: Zotero → Edit → Settings → Advanced → Data Directory Location (default: `C:\Users\YourName\Zotero`)
> - **macOS**: Zotero → Settings → Advanced → Data Directory Location (default: `~/Zotero`)
> - **Linux**: default `~/Zotero`

### Step 3: Use It

Just talk to Claude naturally:```
# One command to read a full paper:
/annota-read "path/to/paper.pdf"

# Or natural language:
# Highlight the findings in this paper's abstract in green
"/Users/yourname/Zotero/storage/ABCD1234/paper.pdf"

Or use slash commands:```
/annota-read "path/to/paper.pdf"
/annota-annotate "path/to/paper.pdf"
/annota-summarize "path/to/paper.pdf"
/annota-review "path/to/paper.pdf" ISCA


> **macOS path tip:** Drag a file from Finder into the terminal to get its full path, or right-click → "Copy as Pathname".

### (Optional) Install Skills Globally```bash
# Make skills available in all projects
cp -r .claude/skills/ ~/.claude/skills/

📖 Usage Examples

Example 1: Highlight Key Findings

Input:```
把这篇论文摘要中的发现结果用绿色标出来
(Highlight the findings in this paper's abstract in green)
"E:\Zotero\storage\ABCD1234\Song et al. - 2025 - AI washing.pdf"


**Result:**

*AI identifies findings in the abstract and highlights them in green*

---

### Example 2: Annotate Hypotheses & Theories

**Input:**```
标注论文中的假设(H1, H2),并用中文解释每个假设的理论基础
(Annotate the hypotheses (H1, H2) and explain the theoretical basis of each in Chinese)

Result:

Hypotheses highlighted in yellow, with Chinese explanation notes for the underlying theory


Example 3: Explain Formulas

Input:```
解释论文中的核心公式,添加中文注释
(Explain the key formulas in this paper, add Chinese annotations)


**Result:**

*DID model formula annotated with variable explanations in Chinese*

---

### Example 4: Policy Implications & Conclusion Notes

**Input:**```
标注结论部分的政策启示,添加中文总结笔记
(Highlight policy implications in the conclusion, add a Chinese summary note)

Result:

Conclusion highlighted with a structured policy implications note


Example 5: Full Paper Reading Notes

Input:```
/annota-summarize "path/to/paper.pdf"


**Result:**

*AI generates a complete reading summary: topic, research question, method, key findings, and implications*

---

### Example 6: Detailed Paragraph-by-Paragraph Notes

**Input:**```
逐段阅读这篇论文,为每个重要段落添加中文批注
(Read this paper paragraph by paragraph, add Chinese annotations to each important section)

Result:

Each important paragraph gets a Chinese annotation explaining the content


Example 7: The AI Workflow in Action

Here's what Claude Code looks like when processing a paper:

Claude creates a task list, reads the PDF, and calls MCP tools to create annotations step by step


🎨 Color Convention

Color Code Use for
🟡 Yellow #ffd400 Default / general highlights
🟢 Green #28CA42 Results, findings, data
🔵 Blue #2EA8E5 Methods, definitions, algorithms
🔴 Red #ff6666 Limitations, issues, problems
🟣 Purple #a28ae5 Contributions, novelty

⚡ How It Handles Large PDFs

For papers >10 pages, a two-phase workflow avoids context overflow:```
Phase 1 — Understand (lightweight)
get_pdf_text_bulk(pdf, skip_refs=True)
→ Full text without coordinates
→ AI identifies which sentences to annotate

Phase 2 — Annotate (precise)
get_pdf_layout_text(pdf, target_page_only)
→ Coordinates for 1–2 target pages
batch_annotate(pdf, all_annotations)
→ Write everything in one call


**Real-world performance:**

| Paper | Pages | Old approach | New approach | Savings |
|-------|-------|-------------|-------------|---------|
| Conference paper | 2 pages | 41 KB coords | 15 KB text | **63%** |
| Journal article | 21 pages | 21 pages extracted | 13 pages (refs skipped at p.13) | **38%** |
| Survey paper | 19 pages | 19 pages extracted | 10 pages (refs skipped at p.10) | **47%** |

---

## 📁 Project Structure```
annota/
├── annota/                        # MCP Server (Python)
│   ├── server.py                  # 9 tool registrations
│   ├── zotero_db.py               # SQLite read/write layer
│   ├── pdf_tools.py               # PyMuPDF text extraction
│   └── config.py                  # Constants & configuration
├── .claude/skills/                # Claude Code Skills
│   ├── annota-annotate/SKILL.md   # /annota-annotate
│   ├── annota-summarize/SKILL.md  # /annota-summarize
│   └── annota-review/SKILL.md     # /annota-review
├── docs/                          # Design documents
│   ├── annota-guide.md            # Usage guide (CN)
│   ├── large-pdf-design.md        # Large PDF handling design
│   ├── dev-notes.md               # Pitfalls & solutions
│   └── commercial-plan.md         # Commercialization plan
├── assets/                        # Screenshots
└── README.md

⚠️ Known Limitations & Disclaimer

> Database Direct Access: Annota writes annotations directly to the Zotero SQLite database, which bypasses Zotero's internal consistency mechanisms. This is a design choice to enable fully offline, local-first annotation workflows without depending on external services. Users are responsible for their own database — please back up your zotero.sqlite before use. We plan to migrate to the official Zotero Web API / Local API in future versions.

Limitation Workaround Planned Fix
Direct SQLite write (not officially supported) Back up your database before use Migrate to Zotero Local API / Web API
Write ops need Zotero closed Close Zotero before annotating Local API bridge
References detection is heuristic Pass skip_refs=False if needed Improve heuristics
Tested primarily on Windows Should work on macOS/Linux — paths auto-detected Community testing welcome

🗺 Roadmap

  • [ ] Zotero Local API / Web API — Migrate from direct SQLite to official API for safer writes
  • [ ] More skills — /compare-papers, /extract-tables, /literature-map
  • [ ] Prompt template marketplace — Share and reuse annotation rules
  • [ ] Team features — Shared annotation standards for lab groups
  • [ ] Multi-backend — Support Adobe Acrobat, Endnote, and other PDF tools

🤝 Contributing

Issues and PRs are welcome! If you have ideas for new skills or tools, please open an issue.

📄 License

MIT — Use it freely for research and commercial projects.


Built with MCP + Claude Code

If this project helps your research, consider giving it a ⭐

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Zotero MCP 696200ee 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zotero MCP 696200ee 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Zotero MCP 696200ee 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zotero MCP 696200ee 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Zotero MCP 696200ee 能提供哪些能力?

资料显示能力标签包括 搜索、文档处理、数据分析。具体工具清单以官方文档为准。

Zotero MCP 696200ee 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Zotero MCP 696200ee 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。