A Zotero plugin that embeds a MCP server directly inside Zotero, giving AI assistants full read/write access to your reference library through 6 unified tools. 一个 Zotero 插件,在 Zotero 内部嵌入 MCP 服务器,让 AI 助手通过6 个统一工具完整访问你的文献库(读写均支持)。
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"zotero-mcp-neo": {
"url": "http://127.0.0.1:23120/mcp",
"transport": "streamable_http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Drive your research workflow with natural language.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / education
Dynamic problem-solving through sequential thought chains
Persistent memory using a knowledge graph
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Local-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free.
MCP Security Weekly
Get CVE alerts and security updates for Zotero MCP Neo and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Search, Read, Write — Safely.
Drive your research workflow with natural language.
A Zotero 7+ plugin (tested on Zotero 7, 8, and 9) that embeds a Streamable HTTP MCP server directly inside Zotero, giving AI assistants full read/write access to your reference library through 6 unified tools.
Based on the excellent cookjohn/zotero-mcp. The foundational plugin architecture, search engine, PDF processing, annotation extraction, semantic search, and more all originate from there. Neo builds upon this by consolidating the MCP API into 6 unified tools with a dryRun-first safety model. See Design Philosophy.
| 6 unified tools | ![]() |
| Library structure browsing | ![]() |
| **Write operations ** | ![]() |
| Paper import workflow | ![]() |
| Settings | ![]() |
| Skim library | ![]() |
| Close reading | ![]() |
| Original | Neo | |
|---|---|---|
| Tools | 20+ individual tools | 6 unified tools (find / list / read / write / status / task) |
| Output control | mode parameter | Explicit sections / include / page |
| Response | AI instruction wrappers | Raw data only |
| Write safety | Direct execution | dryRun-first + layered permissions |
Everything else — search engine, PDF extraction, annotation handling, semantic search, client config generator — is inherited from the original project.
.xpi from ReleasesTools → Add-ons → gear icon → Install Add-on From File...After installation, Zotero’s built-in add-on updater can fetch newer versions from GitHub (the plugin ships an update_url pointing at the published update.json). Use Check for Updates in the Add-ons manager when you want to upgrade manually.
Zotero → Edit → Settings → Zotero MCP Neo:
23120Write access: The default level is Create (new items and notes, organize collections). If you need move, delete, or full in-place edits, open Write Access in the same settings page and switch to Full or Custom.
You need both an MCP connection (so tools are available) and the Agent Skill (so the model follows safe write patterns). Do them in order:
Add this to your AI client's MCP configuration:
{
"mcpServers": {
"zotero-mcp-neo": {
"transport": "streamable_http",
"url": "http://127.0.0.1:23120/mcp"
}
}
}
Where to put this config
| Client | Config location |
|---|---|