Zotero Dev MCP Server

MCP server for Zotero plugin development

Local serverstdioTypeScript

What is the Zotero Dev MCP server?

Zotero Dev MCP server exists for a simple reason — assistants are far more useful when they can act on Zotero Dev directly instead of describing what you should do. MCP server for Zotero plugin development.

What you get

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.

What the assistant can call

Once Zotero Dev is connected, these are the calls the assistant has available:

  • 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
  • zotero_click_element — Click an element by CSS selector (toolbar/menu button, preference control, list row). Pierces shadow DOM; index picks among multiple matches
  • zotero_send_keys — Type text into an input/textarea/contenteditable (focuses it first, fires input/change). Optional clear and pressEnter
  • 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

Configuration and credentials

You will need 3 environment variables: ZOTERO_RDP_PORT, ZOTERO_RDP_HOST, ZOTERO_PROFILE_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • 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

Setting it up

Installation goes through your MCP client rather than a global install: point it at install-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Zotero Dev's toolset — zotero_screenshot, zotero_inspect_element, zotero_get_dom_tree and 11 more — is a fair guide to whether it matches your workflow. It is maintained by introfini; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zotero Dev.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the zotero dev mcp server does with a few real requests.

Available tools

ToolWhat it does
zotero_screenshotCapture window, element, or region screenshots
zotero_inspect_elementFind elements by CSS selector
zotero_get_dom_treeGet DOM structure of a window/panel
zotero_get_stylesGet computed CSS styles for element
zotero_list_windowsList all open Zotero windows
zotero_click_elementClick 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_keysType text into an input/textarea/contenteditable (focuses it first, fires input/change). Optional clear and pressEnter.
zotero_execute_jsExecute JavaScript in Zotero's privileged context. Auto-wraps code with top-level return statements in IIFE.
zotero_inspect_objectExplore Zotero APIs - list methods and properties of any object (e.g., Zotero.Items)
zotero_open_preferencesOpen Zotero's settings window, optionally to a specific pane (built-in or plugin)
zotero_search_prefsSearch/discover preferences by pattern (e.g., find all prefs containing "debug")
zotero_get_prefGet a preference value
zotero_set_prefSet a preference value
zotero_scaffold_buildBuild plugin (dev or production mode)

How to install the Zotero Dev MCP server

{
  "mcpServers": {
    "zotero-dev": {
      "command": "npx",
      "args": ["-y", "@introfini/mcp-server-zotero-dev@1.1.2"],
      "env": {
        "ZOTERO_RDP_PORT": "6101"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • 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
VariableDescriptionRequired
ZOTERO_RDP_PORTConfiguration value read at startup.Optional
ZOTERO_RDP_HOSTEndpoint or connection string the server talks to.Optional
ZOTERO_PROFILE_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Zotero Dev to zotero screenshot.
  • Use Zotero Dev to zotero inspect element.
  • Use Zotero Dev to zotero get dom tree.

Frequently asked questions

It connects Zotero Dev to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (zotero_screenshot, zotero_inspect_element, zotero_get_dom_tree, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Zotero Dev directly.