MCP Server Zotero Dev 8265abc2

MCP运维云端

提供方 introfini · 包名 install-mcp

运维云端 stdio · 本地进程 无需鉴权 社区 / 第三方 ClaudeCursorWindsurfCline
查看接入方式

MCP Server Zotero Dev是一个为Zotero插件开发提供AI辅助支持的工具,支持UI检查、JavaScript执行、构建工具、日志调试、插件管理和数据库访问等功能。

一句话选型结论

按资料字段整理

MCP Server Zotero Dev 8265abc2 属于运维云端类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude、Cursor、Windsurf 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

Zotero插件开发TypeScript本地部署AI辅助开发UI检查JavaScript执行构建工具

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
npx -y install-mcp @introfini/mcp-server-zotero-dev --client claude-code

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude、Cursor、Windsurf,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP Server Zotero Dev 8265abc2当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方introfini上游标注的维护方 introfini
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时install-mcp · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

MCP Server Zotero Dev

Give your AI assistant superpowers for Zotero plugin development

Architecture · Getting Started · Available Tools


A Model Context Protocol (MCP) server that enables AI assistants like Claude, Cursor, and Windsurf to build, test, and debug Zotero 7, 8, 9, and 10 plugins. Screenshots, DOM state, debug logs, and JavaScript execution give the AI rich context to understand what's happening—and tools to help you fix it.

✨ Features

Category Capabilities
🎯 UI Inspection Screenshots, DOM tree, element finding, computed styles
🖱️ UI Interaction Click elements and type text (shadow-DOM aware)
💻 JS Execution Run code in Zotero context, inspect APIs, test snippets
🔧 Build Tools Scaffold integration for build, serve, hot reload
📋 Logs & Errors Stream debug output, error console, watch for issues
🗃️ Database Read-only access to zotero.sqlite for debugging
🔌 Plugin Management Install, reload, list plugins

🚀 Quick Start

Prerequisites

  • Node.js 20+ and npm
  • Zotero 7+ — Works on all Zotero 7, 8, 9, and 10 builds (release, beta, dev)
  • For plugin development: zotero-plugin-scaffold

1. Install MCP Server

Use install-mcp to add the server to your AI assistant:```bash
npx -y install-mcp @introfini/mcp-server-zotero-dev --client claude-code


Supported clients: `claude-code`, `cursor`, `windsurf`, `vscode`, `cline`, `roo-cline`, `claude`, `zed`, `goose`, `warp`, `codex`

Claude Code```bash
npx -y install-mcp @introfini/mcp-server-zotero-dev --client claude-code

Cursor```bash
npx -y install-mcp @introfini/mcp-server-zotero-dev --client cursor


VS Code / Copilot```bash
npx -y install-mcp @introfini/mcp-server-zotero-dev --client vscode

Windsurf```bash
npx -y install-mcp @introfini/mcp-server-zotero-dev --client windsurf


Manual Configuration

Add to your MCP client config:```json
{
  "mcpServers": {
    "zotero-dev": {
      "command": "npx",
      "args": ["-y", "@introfini/mcp-server-zotero-dev@1.1.1"],
      "env": {
        "ZOTERO_RDP_PORT": "6100"
      }
    }
  }
}

> Version & updates: pin an exact version as shown above. A bare npx (no version) keeps running whatever npx cached and won't pick up new releases, so always include a version and -y (without -y, npx hangs waiting for an install prompt). Bump the pinned version to upgrade, or use @latest to always fetch the newest at launch (auto-updates, but a bad release would run automatically and it adds a registry check on every start). Note that install-mcp may write a config without -y or a version, so the manual configuration above is the most robust path.

Restart your AI assistant after adding the configuration.

2. Install MCP Bridge Plugin in Zotero

Download zotero-mcp-bridge.xpi and install:

  1. In Zotero: Tools → Plugins
  2. Click ⚙️ → Install Plugin From File
  3. Select the downloaded .xpi file
  4. Restart Zotero

> This lightweight plugin enables the Remote Debugging Protocol when Zotero starts. It only needs to be installed once and works on all Zotero 7+ builds (release, beta, and dev).

3. Start Developing!

Just open Zotero normally and ask your AI assistant:

> "Take a screenshot of Zotero and list installed plugins"

That's it! No special launch flags, no configuration. 🎉


🧰 Available Tools (28 total)

UI Inspection — Screenshots, DOM, styles

Tool Description
zotero_screenshot Capture window, element, or region screenshots
zotero_inspect_element Find elements by CSS selector
zotero_get_dom_tree Get DOM structure of a window/panel
zotero_get_styles Get computed CSS styles for element
zotero_list_windows List all open Zotero windows

> Screenshot Targets: Main window, preferences, PDF reader, dialogs, or any element by selector. Use highlightSelector to add a red border before capture.

UI Interaction — Click and type in the Zotero UI

Tool Description
zotero_click_element Click an element by CSS selector (toolbar/menu button, preference control, list row). Pierces shadow DOM; index picks among multiple matches; mouseEvents synthesizes a full mouse sequence.
zotero_send_keys Type text into an input/textarea/contenteditable (focuses it first, fires input/change). Optional clear and pressEnter.

> Resolution tries light DOM first, then pierces open shadow roots (Zotero's XUL custom elements keep internals in shadow DOM). Limitation: cannot dismiss a blocking native modal dialog (Services.prompt.confirmEx) — its nested modal loop blocks the eval thread these tools run on.

JavaScript Execution — Run code in Zotero context

Tool Description
zotero_execute_js Execute JavaScript in Zotero's privileged context. Auto-wraps code with top-level return statements in IIFE.
zotero_inspect_object Explore Zotero APIs - list methods and properties of any object (e.g., Zotero.Items)
zotero_open_preferences Open Zotero's settings window, optionally to a specific pane (built-in or plugin)
zotero_search_prefs Search/discover preferences by pattern (e.g., find all prefs containing "debug")
zotero_get_pref Get a preference value
zotero_set_pref Set a preference value

> Examples: Zotero.Items.getAll(1), Zotero.Prefs.get('export.quickCopy.setting'), ZoteroPane.getSelectedItems()
>
> Tip: Use zotero_inspect_object to explore APIs before writing code. Use zotero_search_prefs to discover preference keys.

Build & Scaffold — Integration with zotero-plugin-scaffold

Tool Description
zotero_scaffold_build Build plugin (dev or production mode)
zotero_scaffold_serve Start dev server with hot reload
zotero_scaffold_lint Run ESLint on plugin source
zotero_scaffold_typecheck Run TypeScript type checking

Logs & Debugging — Error console and debug output

Tool Description
zotero_read_logs Read debug output (Zotero.debug)
zotero_read_errors Read error console entries
zotero_watch_logs Stream logs in real-time
zotero_clear_logs Clear log buffer

Plugin Management — Install, reload, inspect

Tool Description
zotero_plugin_reload Hot reload your dev plugin
zotero_plugin_install Install plugin from XPI path
zotero_plugin_list List installed plugins with version/status

Database Access — Read-only SQLite access

Tool Description
zotero_db_query Execute SELECT query on zotero.sqlite
zotero_db_schema Get table schema information
zotero_db_stats Get database statistics (items, attachments, collections, size)

> Note: Database access is read-only and requires Zotero to be closed, or uses a copy of the database.


🏗️ Architecture```

┌─────────────────────────────────────────────────────────────────┐
│ AI Assistant │
│ (Claude, Cursor, Windsurf) │
└─────────────────────────┬───────────────────────────────────────┘
│ MCP Protocol (stdio)
▼
┌─────────────────────────────────────────────────────────────────┐
│ MCP Server (Node.js/TypeScript) │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────────────┐ │
│ │ Scaffold │ │ RDP │ │ Database │ │
│ │ Integration │ │ Client │ │ Reader │ │
│ └──────────────┘ └──────┬───────┘ └──────────────────────┘ │
└─────────────────────────────┼───────────────────────────────────┘
│ Firefox RDP (port 6100)
▼
┌─────────────────────────────────────────────────────────────────┐
│ Zotero Application │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ MCP Bridge for Zotero │ │
│ │ Starts DevToolsServer on launch │ │
│ └──────────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Firefox DevTools Server (built-in) │ │
│ │ JS Execution • DOM • Console • Screenshots │ │
│ └──────────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Your Plugin (dev) │ │
│ └──────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────┘


**Why this approach?**

- ✅ **Lightweight plugin** — Just enables RDP, Firefox DevTools does the rest
- ✅ **Zero-config after install** — Just open Zotero normally, no special flags
- ✅ **Rich AI context** — Screenshots, DOM, and logs help the AI understand your plugin's state
- ✅ **Hot reload** — Integrates with zotero-plugin-scaffold for instant feedback
- ✅ **Full Zotero access** — Execute any Zotero API in the privileged context
- ✅ **Cross-platform** — Works on Linux, Windows, macOS

---

## 🔧 Environment Variables

| Variable | Description | Default |
|----------|-------------|---------|
| `ZOTERO_RDP_PORT` | Remote debugging port | `6100` |
| `ZOTERO_RDP_HOST` | Debugging host | `127.0.0.1` |
| `ZOTERO_DATA_DIR` | Path to Zotero data directory | Auto-detect |
| `ZOTERO_PROFILE_PATH` | Path to Zotero profile | Auto-detect |

---

## 🔌 Changing the RDP Port

The bridge listens on port `6100` by default. You only need to change it if you run **two Zotero instances at the same time** (a normal profile and a development one, say), or if another process already holds 6100.

The port lives on **both sides of the bridge**, and both have to agree on it.

**1. Zotero side** — set the plugin preference:

1. **Settings → Advanced → Config Editor**, and accept the warning
2. Search for `extensions.mcp-rdp.port`
3. If it doesn't exist, create it: select **Number**, name it `extensions.mcp-rdp.port`, and enter your port
4. **Restart Zotero** — the listener only opens at startup

> **Watch the type.** The Config Editor pre-selects **Boolean**. Creating the preference without switching to **Number** stores `true` instead of a port, and Zotero then opens the bridge on a local pipe rather than a TCP port — the debug log reports success while no MCP client can connect.

**2. Client side** — set `ZOTERO_RDP_PORT` to the same value in your MCP client config:```json
{
  "mcpServers": {
    "zotero-dev": {
      "command": "npx",
      "args": ["-y", "@introfini/mcp-server-zotero-dev@1.1.2"],
      "env": {
        "ZOTERO_RDP_PORT": "6101"
      }
    }
  }
}

> Change both or neither. Moving only one side disconnects the bridge: Zotero listens on one port while the client keeps dialing the other.

Actually running two instances

Launching Zotero a second time hands you the window you already have — like Firefox, it forwards to the running instance instead of starting another. A second instance needs its own profile and -no-remote:```bash

macOS; adjust the binary path on Windows/Linux

MOZ_NO_REMOTE=1 "/Applications/Zotero.app/Contents/MacOS/zotero" -P <profile-name> -no-remote


Give that profile its own `extensions.mcp-rdp.port` and the two bridges stay out of each other&#x27;s way. Verified with 9.0.6 on 6100 and 10.0-beta.22 on 6101 at the same time.

&gt; **Requires MCP Bridge plugin 1.0.5 or later.** In 1.0.4 and earlier, `extensions.mcp-rdp.port` was read under the wrong preference branch and silently ignored, so the bridge stayed on 6100 no matter what you set. If you configured a custom port against an older build, it is stored as `extensions.zotero.extensions.mcp-rdp.port` — that name still works, but prefer the one above.

### Disabling the bridge

Set `extensions.mcp-rdp.enabled` to `false` (**Boolean**) in the Config Editor and restart Zotero. The plugin stays installed but opens no listener, and no MCP client can reach Zotero until you set it back to `true`.

### Checking what the bridge did

The plugin appends one line per lifecycle **transition** to `mcp-rdp-events.log` in your Zotero **profile** directory: startup, listener open, listener down, listener recovered, listener flapping, shutdown. It survives restarts and is readable without Zotero running, which makes it the first place to look when an MCP client reports `Cannot connect to Zotero RDP`:```
2026-09-17T07:52:36.201Z startup v1.0.5 reason=1
2026-09-17T07:52:37.914Z listener DOWN on port 6177 - failed to open at startup: port 6177 does not answer (held by another process?)
2026-09-17T07:53:46.552Z listener RECOVERED on port 6177 after 6 failed checks, 69s down
2026-09-17T08:01:12.083Z shutdown v1.0.5 reason=2

What to read from it:

  • listener DOWN … failed to open at startup — something else holds the port: another Zotero instance, a previous one that has not released it, or a process that answers on the port without speaking RDP. The reason after the colon says which of the last two it is.
  • listener DOWN … stopped answering — the listener was up and then died. The health check reopens it; the next line tells you when that worked and how long the gap was.
  • listener RECOVERED … after N failed checks — the bridge came back on its own. A large N means the port was held for a long time; nothing is logged per attempt, so the file stays short no matter how long the outage.
  • listener FLAPPING, later closed by listener STEADY … after N flaps — the listener keeps dying and coming straight back on the first reopen. That is a different fault from an outage: the port is yours, something is tearing the listener down. The whole run costs these two lines however long it goes on, so N is the number to report if you open an issue.
  • A startup with no shutdown before it — Zotero was killed or crashed rather than exiting cleanly. Usually the answer to "the bridge stopped working" is simply that Zotero is not running.
  • No new lines at all — the plugin never started: disabled by preference, or not installed in the profile you are actually running.

log() output goes to dump() (lost unless Zotero was started from a console) and Zotero.debug() (a no-op unless debug output is enabled), so this file is the only durable record of a boot-time failure. A healthy session adds three lines (startup, open, shutdown); an outage adds two more, and a run of flaps two more, whatever their length. No failure mode writes per tick.


📸 Screenshot Examples```typescript

// Capture main Zotero window
await zotero_screenshot({ target: 'main-window' });

// Capture your plugin's panel with highlight
await zotero_screenshot({
target: 'element',
selector: '#my-plugin-panel',
highlightSelector: '#my-plugin-button'
});

// Capture a specific window by ID (use zotero_list_windows to find IDs)
await zotero_screenshot({
target: 'window',
windowId: 12345
});

// Capture element after triggering UI action
await zotero_execute_js({ code: 'document.querySelector("#menu").click()' });
await zotero_screenshot({ target: 'element', selector: 'menupopup[state="open"]' });


---

## 🧑‍💻 Development```bash
# Clone and install
git clone https://github.com/introfini/mcp-server-zotero-dev.git
cd mcp-server-zotero-dev
npm install

# Build everything
npm run build

# Build individual packages
npm run build:server
npm run build:plugin

# Run tests
npm test

# Development mode (watch)
npm run dev

Project Structuremcp-server-zotero-dev/ ├── packages/ │ ├── mcp-server/ # MCP server (npm package) │ │ ├── src/ │ │ │ ├── index.ts # MCP server entry │ │ │ ├── rdp/ # RDP client │ │ │ ├── tools/ # Tool implementations │ │ │ └── prompts/ # Slash commands │ │ └── package.json │ │ │ └── zotero-plugin-mcp-rdp/ # Tiny Zotero plugin (.xpi) │ ├── src/ │ │ └── bootstrap.js # Starts RDP server (shipped verbatim) │ ├── addon/ │ │ └── manifest.json │ └── package.json │ ├── docs/ # Documentation └── package.json # Monorepo root


📚 Resources

  • Architecture & Technical Learnings — Deep dive into RDP protocol, actor hierarchy, and common pitfalls
  • Zotero Plugin Development — Official docs
  • Zotero 10 for Developers — Migration guide for the latest major
  • Zotero 7 for Developers — Migration guide
  • zotero-plugin-scaffold — Build tooling
  • zotero-plugin-template — Starter template
  • zotero-plugin-toolkit — API helpers
  • Firefox RDP Protocol — Protocol docs

🤝 Contributing

Contributions are welcome. See CONTRIBUTING.md for setup, test conventions and the codebase-specific rules worth knowing before you start.

The short version:

  1. Follow existing code patterns
  2. Add tests for new features, and skip rather than fail when Zotero is not running
  3. Update documentation
  4. There is no CI, so run npm run build, npm run typecheck, npm run lint and npm test yourself, and say in the PR which Zotero version you verified against

📄 License

MIT © introfini


Acknowledgments

  • Built for the Zotero plugin developer community
  • Integrates with zotero-plugin-scaffold by @windingwind
  • Leverages Firefox DevTools RDP for reliable communication

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
MCP Server Zotero Dev 8265abc2 怎么安装?

在客户端按下面的安装命令接入:npx -y install-mcp @introfini/mcp-server-zotero-dev --client claude-code。对应的包名是 install-mcp。装完在客户端配置里引用同一个包或端点。

MCP Server Zotero Dev 8265abc2 怎么在 Claude、Cursor、Windsurf 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

MCP Server Zotero Dev 8265abc2 收费吗?

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

MCP Server Zotero Dev 8265abc2 需要 API Key 吗?

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

MCP Server Zotero Dev 8265abc2 支持哪些客户端?

资料标注支持 Claude、Cursor、Windsurf、Cline、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

MCP Server Zotero Dev 8265abc2 能提供哪些能力?

资料显示能力标签包括 构建工具、TypeScript、Claude、AI代理。具体工具清单以官方文档为准。

MCP Server Zotero Dev 8265abc2 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

MCP Server Zotero Dev 8265abc2 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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