Stdio MCP adapter for Zotero Local MCP Bridge HTTP endpoint.
Most developer tooling work still happens through a UI a human drives. Zotero MCP server moves it into the conversation instead. Stdio MCP adapter for Zotero Local MCP Bridge HTTP endpoint.
Use a Zotero plugin-hosted MCP endpoint to let local agents manage a local Zotero library safely.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The server publishes 13 tools. What each one is for:
Area — CapabilityItem — Current settingEndpoint — http://127.0.0.1:23119/zotero-local-mcp-bridge/mcpMode — Behaviorreadonly — Blocks all writesaskforapprove — The agent asks the user for approval after dry-runyolo — Ordinary writes may auto-execute when the plan allows it; high-risk or future unrecoverable operations still require explicit confirmationFile — Purposezotero-local-mcp-bridge.xpi — Zotero pluginLanguage — SkillEnglish — skills/zotero-local-mcp-bridge/SKILL.mdChinese — skills/zotero-local-mcp-bridge-zh-cn/SKILL.mdConfiguration is passed through the environment: ZOTERO_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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's toolset — Area, Item, Endpoint and 10 more — is a fair guide to whether it matches your workflow. It is maintained by phoenix_chen; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Zotero's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Area | Capability |
| Item | Current setting |
| Endpoint | http://127.0.0.1:23119/zotero-local-mcp-bridge/mcp |
| Mode | Behavior |
| readonly | Blocks all writes |
| askforapprove | The agent asks the user for approval after dry-run |
| yolo | Ordinary writes may auto-execute when the plan allows it; high-risk or future unrecoverable operations still require explicit confirmation |
| File | Purpose |
| zotero-local-mcp-bridge.xpi | Zotero plugin |
| Language | Skill |
| English | [skills/zotero-local-mcp-bridge/SKILL.md](skills/zotero-local-mcp-bridge/SKILL.md) |
| Chinese | [skills/zotero-local-mcp-bridge-zh-cn/SKILL.md](skills/zotero-local-mcp-bridge-zh-cn/SKILL.md) |
| No. | Operation |
Generic stdio MCP configuration:
```json
{
"mcpServers": {
"zotero-local-mcp-bridge": {
"type": "stdio",
"command": "zotero-local-mcp-bridge-stdio",
"args": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ZOTERO_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.