
Mcp Server Zotero Dev
io.github.introfiniPublished by GitHub account introfiniv1.1.4Updated Oct 24, 2026
MCP server enabling AI assistants to build, test, and debug Zotero plugins
Overview
Local MCP server that lets an AI assistant build, test and debug Zotero 7+ plugins by driving a running Zotero over Firefox's Remote Debugging Protocol.
- What you can do
- Connect to Zotero and run JavaScript in its privileged context, read and set preferences, inspect objects and open the preferences window
- Inspect the UI: take screenshots, find DOM elements by CSS selector, read DOM trees and computed styles, list open windows
- Read, watch and clear Zotero debug logs and error-console errors
- Build plugins with zotero-plugin-scaffold, run a hot-reload dev server, lint with ESLint and type-check TypeScript
- List, install from a local XPI and reload Zotero plugins
- Run read-only SELECT queries and inspect schema and statistics of Zotero's database
- When to use it
- Use it when you are developing or maintaining a Zotero 7+ plugin and want an assistant to inspect the live Zotero UI, execute code, read logs and errors, and run build and reload steps without switching tools.
- Requirements
- Runs locally via npx or a global npm install; needs Node.js 20 or newer, Zotero 7+ running, and the separate MCP Bridge for Zotero plugin installed so a DevTools server listens on port 6100. Optional environment variables ZOTERO_RDP_HOST, ZOTERO_RDP_PORT, ZOTERO_DATA_DIR and ZOTERO_PROFILE_PATH override defaults.
Installation
In SourceWeft
- Open Mcp Server Zotero Dev in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Server for Zotero Plugin Development
An MCP (Model Context Protocol) server that enables AI assistants to build, test, and debug Zotero 7+ plugins. It provides 25 tools for UI inspection, JavaScript execution, build integration, logging, database access, and plugin management.
How it works: Zotero 7+ is built on Firefox ESR, so this server communicates with Zotero through Firefox's built-in Remote Debugging Protocol (RDP). A small companion plugin (MCP Bridge for Zotero) starts the DevTools server inside Zotero, and this MCP server connects to it.
Prerequisites
- Node.js >= 20
- Zotero 7+ (release, beta, or dev build)
- MCP Bridge for Zotero plugin installed in Zotero — download the latest XPI
Installing the MCP Bridge plugin
- Download
zotero-mcp-bridge-*.xpifrom GitHub Releases - In Zotero: Tools > Add-ons > gear icon > Install Add-on From File...
- Select the downloaded
.xpifile - Restart Zotero
The plugin automatically starts a DevTools server on port 6100 when Zotero launches.
Setup
Claude Desktop
Add to your claude_desktop_config.json:
Claude Code
Cursor / Windsurf / Other MCP clients
Configure the MCP server with:
- Command:
npx - Arguments:
-y @introfini/mcp-server-zotero-dev
Or install globally:
Tools (25)
JavaScript Execution & Inspection
UI Inspection
Logging & Debugging
Build Integration
Plugin Management
Database Access (Read-only)
Prompts (5)
Configuration
Environment variables (all optional):
Troubleshooting
"Cannot connect to Zotero"
- Make sure Zotero is running
- Verify the MCP Bridge plugin is installed (Tools > Add-ons)
- Restart Zotero after installing the plugin
- Check port 6100 is not blocked:
lsof -i :6100
"Port already in use"
- Another Zotero instance may be running, or Zotero was started with the
-debuggerflag (which uses port 6000). The MCP Bridge uses port 6100 to avoid conflicts.
License
MIT
Source: packages/mcp-server/README.md at commit 24f8f50
Tools
0Version history
2- v1.1.4LatestSep 20, 2026
- v1.1.3Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts