zotero-bridge 1.0.1 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1 @@
1
+ ghu_v3cACeuQsFRhTZvUunz7CoS41GZgN40HEHjq
@@ -0,0 +1 @@
1
+ {"token":"eyJhbGciOiJFZERTQSIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJtY3AtcmVnaXN0cnkiLCJleHAiOjE3Njk5Mjc4NDAsIm5iZiI6MTc2OTkyNzU0MCwiaWF0IjoxNzY5OTI3NTQwLCJhdXRoX21ldGhvZCI6ImdpdGh1Yi1hdCIsImF1dGhfbWV0aG9kX3N1YiI6IkNvbWJqZWxseXNoZW4iLCJwZXJtaXNzaW9ucyI6W3siYWN0aW9uIjoicHVibGlzaCIsInJlc291cmNlIjoiaW8uZ2l0aHViLkNvbWJqZWxseXNoZW4vKiJ9XX0.XMdX_zJ_KZUeAovcxR3NFfK8RA29e6zSHZsJos1WTk-B4nMPRn9j-5NGZskuWQiAhQeDUKlOI7NF8TflF-DoBA","expires_at":1769927840}
package/LICENSE CHANGED
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 Combjellyshen
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2025 MCP Contributors
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,324 +1,153 @@
1
- # ZoteroBridge
2
-
3
- <p align="right">
4
- <a href="README.md">简体中文</a> | <a href="README-en.md">English</a>
5
- </p>
6
-
7
- <p align="center">
8
- <b>Model Context Protocol (MCP) Server for Zotero SQLite Database</b>
9
- </p>
10
-
11
- <p align="center">
12
- <a href="https://www.zotero.org/"><img src="https://img.shields.io/badge/Zotero-7.0+-red" alt="Zotero"></a>
13
- <a href="https://nodejs.org/"><img src="https://img.shields.io/badge/Node.js-18+-green" alt="Node.js"></a>
14
- <a href="https://www.typescriptlang.org/"><img src="https://img.shields.io/badge/TypeScript-5.0+-blue" alt="TypeScript"></a>
15
- <a href="https://modelcontextprotocol.io/"><img src="https://img.shields.io/badge/MCP-1.0-purple" alt="MCP"></a>
16
- <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow" alt="License"></a>
17
- </p>
18
-
19
- ---
20
-
21
- ## 📚 项目概述
22
-
23
- ZoteroBridge 是一个基于 Model Context Protocol (MCP) 的服务器,它直接连接 Zotero 的 SQLite 数据库 (`zotero.sqlite`),为 AI 助手(如 Claude、ChatGPT 等)提供与 Zotero 文献库交互的能力。
24
-
25
- ### 主要功能
26
-
27
- - 🗂️ **目录管理** - 创建、重命名、移动、删除 Zotero 集合(文件夹)
28
- - 🏷️ **标签管理** - 添加、删除、查询文献标签
29
- - 📖 **文献操作** - 搜索文献、获取详情、管理集合关系
30
- - 📝 **摘要管理** - 读取和设置文献摘要、添加笔记
31
- - 📄 **PDF 处理** - 提取 PDF 全文、生成摘要、全文搜索
32
-
33
- ---
34
-
35
- ## 🚀 快速开始
36
-
37
- ### 系统要求
38
-
39
- - Node.js 18.0 或更高版本
40
- - Zotero 7.0 或更高版本
41
- - 一个支持 MCP 的 AI 客户端(如 Claude Desktop、Cursor 等)
42
-
43
- ### 安装
44
-
45
- ```bash
46
- # 克隆项目
47
- git clone https://github.com/Combjellyshen/ZoteroBridge.git
48
- cd ZoteroBridge
49
-
50
- # 安装依赖
51
- npm install
52
-
53
- # 构建项目
54
- npm run build
55
- ```
56
-
57
- ### 配置 AI 客户端
58
-
59
- #### Claude Desktop
60
-
61
- Claude Desktop 的配置文件中添加:
62
-
63
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
64
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
65
-
66
- ```json
67
- {
68
- "mcpServers": {
69
- "zotero-bridge": {
70
- "command": "node",
71
- "args": ["path/to/ZoteroBridge/dist/index.js"],
72
- "env": {}
73
- }
74
- }
75
- }
76
- ```
77
-
78
- #### Cursor IDE
79
-
80
- 在项目根目录创建 `.cursor/mcp.json`:
81
-
82
- ```json
83
- {
84
- "mcpServers": {
85
- "zotero-bridge": {
86
- "command": "node",
87
- "args": ["path/to/ZoteroBridge/dist/index.js"]
88
- }
89
- }
90
- }
91
- ```
92
-
93
- #### VS Code Copilot
94
-
95
- 1. 打开 VS Code 设置 (`Ctrl+,`)。
96
- 2. 搜索 `github.copilot.chat.mcpServers`。
97
- 3. 点击 "在 settings.json 中编辑"。
98
- 4. 添加以下配置:
99
-
100
- ```json
101
- "github.copilot.chat.mcpServers": {
102
- "zotero-bridge": {
103
- "command": "node",
104
- "args": ["path/to/ZoteroBridge/dist/index.js"]
105
- }
106
- }
107
- ```
108
- 确保将 `path/to/ZoteroBridge/dist/index.js` 替换为这一文件的实际绝对路径。
109
-
110
- #### 自定义数据库路径
111
-
112
- 如果你的 Zotero 数据库不在默认位置,可以指定路径:
113
-
114
- ```json
115
- {
116
- "mcpServers": {
117
- "zotero-bridge": {
118
- "command": "node",
119
- "args": [
120
- "path/to/ZoteroBridge/dist/index.js",
121
- "--db", "D:/MyZotero/zotero.sqlite"
122
- ]
123
- }
124
- }
125
- }
126
- ```
127
-
128
- ---
129
-
130
- ## 🛠️ 可用工具
131
-
132
- ### 目录/集合管理
133
-
134
- | 工具 | 描述 |
135
- |------|------|
136
- | `list_collections` | 列出所有集合 |
137
- | `get_collection` | 获取集合详情 |
138
- | `create_collection` | 创建新集合 |
139
- | `rename_collection` | 重命名集合 |
140
- | `move_collection` | 移动集合到新父级 |
141
- | `delete_collection` | 删除集合 |
142
- | `get_subcollections` | 获取子集合 |
143
-
144
- ### 标签管理
145
-
146
- | 工具 | 描述 |
147
- |------|------|
148
- | `list_tags` | 列出所有标签 |
149
- | `create_tag` | 创建新标签 |
150
- | `add_tag` | 为文献添加标签 |
151
- | `remove_tag` | 移除文献标签 |
152
- | `get_item_tags` | 获取文献的所有标签 |
153
-
154
- ### 文献操作
155
-
156
- | 工具 | 描述 |
157
- |------|------|
158
- | `search_items` | 按标题搜索文献 |
159
- | `get_item_details` | 获取文献详细信息 |
160
- | `add_item_to_collection` | 将文献添加到集合 |
161
- | `remove_item_from_collection` | 从集合中移除文献 |
162
- | `get_collection_items` | 获取集合中的所有文献 |
163
-
164
- ### 摘要和笔记
165
-
166
- | 工具 | 描述 |
167
- |------|------|
168
- | `get_item_abstract` | 获取文献摘要 |
169
- | `set_item_abstract` | 设置文献摘要 |
170
- | `get_item_notes` | 获取文献笔记 |
171
- | `add_item_note` | 添加笔记到文献 |
172
-
173
- ### PDF 处理
174
-
175
- | 工具 | 描述 |
176
- |------|------|
177
- | `extract_pdf_text` | 提取 PDF 全文 |
178
- | `get_pdf_summary` | 获取 PDF 摘要信息 |
179
- | `get_item_pdfs` | 获取文献的 PDF 附件 |
180
- | `search_pdf` | 在 PDF 中搜索文本 |
181
- | `generate_abstract_from_pdf` | 从 PDF 生成摘要 |
182
-
183
- ### 实用工具
184
-
185
- | 工具 | 描述 |
186
- |------|------|
187
- | `get_database_info` | 获取数据库信息 |
188
- | `raw_query` | 执行原始 SQL 查询(仅 SELECT) |
189
-
190
- ### 标识符搜索 (DOI/ISBN)
191
-
192
- | 工具 | 描述 |
193
- |------|------|
194
- | `find_by_doi` | 通过 DOI 查找文献 |
195
- | `find_by_isbn` | 通过 ISBN 查找文献 |
196
- | `find_by_identifier` | 通过任意标识符(DOI, ISBN, PMID, arXiv)查找文献 |
197
-
198
- ### PDF 注释
199
-
200
- | 工具 | 描述 |
201
- |------|------|
202
- | `get_item_annotations` | 获取文献的所有注释(高亮、批注等) |
203
- | `get_attachment_annotations` | 获取特定附件的注释 |
204
- | `get_annotations_by_type` | 按类型筛选注释(高亮、笔记等) |
205
- | `get_annotations_by_color` | 按颜色筛选注释 |
206
- | `search_annotations` | 在注释内容中搜索 |
207
-
208
- ### 全文搜索
209
-
210
- | 工具 | 描述 |
211
- |------|------|
212
- | `search_fulltext` | 在全文索引中搜索 |
213
- | `get_fulltext_content` | 获取附件的全文内容 |
214
- | `search_fulltext_with_context` | 带上下文的全文搜索 |
215
-
216
- ### 相关文献推荐
217
-
218
- | 工具 | 描述 |
219
- |------|------|
220
- | `get_related_items` | 获取手动关联的相关文献 |
221
- | `find_similar_by_tags` | 根据共同标签查找相似文献 |
222
- | `find_similar_by_creators` | 根据共同作者查找相似文献 |
223
- | `find_similar_by_collection` | 在同一集合中查找相似文献 |
224
-
225
- ---
226
-
227
- ## 📖 使用示例
228
-
229
- ### 在 Claude 中使用
230
-
231
- ```
232
- # 列出所有集合
233
- 请列出我 Zotero 中的所有集合
234
-
235
- # 创建新集合
236
- 帮我创建一个名为"机器学习论文"的新集合
237
-
238
- # 搜索文献
239
- 搜索标题包含"deep learning"的文献
240
-
241
- # 获取 PDF 内容
242
- 提取这篇文献的 PDF 全文并生成摘要
243
-
244
- # 添加标签
245
- 为这篇文献添加"重要"和"待读"标签
246
- ```
247
-
248
- ---
249
-
250
- ## 🏗️ 项目结构
251
-
252
- ```
253
- ZoteroBridge/
254
- ├── src/
255
- │ ├── index.ts # MCP 服务器入口
256
- │ ├── database.ts # Zotero SQLite 数据库操作
257
- │ ├── pdf.ts # PDF 处理模块
258
- │ └── tools.ts # MCP 工具定义
259
- ├── dist/ # 编译输出
260
- ├── package.json
261
- ├── tsconfig.json
262
- └── README.md
263
- ```
264
-
265
- ---
266
-
267
- ## 👨‍💻 开发指南
268
-
269
- ### 开发模式
270
-
271
- ```bash
272
- # 监听文件变化并自动编译
273
- npm run dev
274
- ```
275
-
276
- ### 构建
277
-
278
- ```bash
279
- npm run build
280
- ```
281
-
282
- ### 命令行参数
283
-
284
- ```bash
285
- # 显示帮助
286
- node dist/index.js --help
287
-
288
- # 指定数据库路径
289
- node dist/index.js --db /path/to/zotero.sqlite
290
-
291
- # 只读模式
292
- node dist/index.js --readonly
293
- ```
294
-
295
- ---
296
-
297
- ## ⚠️ 注意事项
298
-
299
- 1. **关闭 Zotero**: 在使用写入功能时,建议关闭 Zotero 客户端以避免数据库锁定
300
- 2. **备份数据**: 修改数据库前建议备份 `zotero.sqlite`
301
- 3. **只读模式**: 如果只需要读取数据,使用 `--readonly` 参数更安全
302
-
303
- ---
304
-
305
- ## 📄 许可证
306
-
307
- 本项目采用 [MIT License](LICENSE) 许可证。
308
-
309
- ---
310
-
311
- ## 🙏 致谢
312
-
313
- - [Zotero](https://www.zotero.org/) - 优秀的开源文献管理工具
314
- - [Model Context Protocol](https://modelcontextprotocol.io/) - AI 工具集成协议
315
- - [cookjohn/zotero-mcp](https://github.com/cookjohn/zotero-mcp) - 项目参考
316
-
317
- ---
318
-
319
- ## 📬 联系方式
320
-
321
- - 作者: Combjellyshen
322
- - GitHub: [https://github.com/Combjellyshen/ZoteroBridge](https://github.com/Combjellyshen/ZoteroBridge)
323
-
324
- 如有问题或建议,欢迎提交 Issue 或 Pull Request!
1
+ # MCP Registry
2
+
3
+ The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
4
+
5
+ [**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
6
+
7
+ ## Development Status
8
+
9
+ **2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
10
+
11
+ **2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
12
+
13
+ Current key maintainers:
14
+ - **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)
15
+ - **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
16
+ - **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
17
+ - **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
18
+
19
+ ## Contributing
20
+
21
+ We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
22
+
23
+ Often (but not always) ideas flow through this pipeline:
24
+
25
+ - **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
26
+ - **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
27
+ - **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work
28
+ - **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
29
+
30
+ ### Quick start:
31
+
32
+ #### Pre-requisites
33
+
34
+ - **Docker**
35
+ - **Go 1.24.x**
36
+ - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
37
+ - **golangci-lint v2.4.0**
38
+
39
+ #### Running the server
40
+
41
+ ```bash
42
+ # Start full development environment
43
+ make dev-compose
44
+ ```
45
+
46
+ This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
47
+
48
+ **Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
49
+
50
+ By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
51
+
52
+ The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
53
+
54
+ <details>
55
+ <summary>Alternative: Running a pre-built Docker image</summary>
56
+
57
+ Pre-built Docker images are automatically published to GitHub Container Registry:
58
+
59
+ ```bash
60
+ # Run latest stable release
61
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
62
+
63
+ # Run latest from main branch (continuous deployment)
64
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
65
+
66
+ # Run specific release version
67
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
68
+
69
+ # Run development build from main branch
70
+ docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
71
+ ```
72
+
73
+ **Available tags:**
74
+ - **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
75
+ - **Continuous**: `main` (latest main branch build)
76
+ - **Development**: `main-<date>-<sha>` (specific commit builds)
77
+
78
+ </details>
79
+
80
+ #### Publishing a server
81
+
82
+ To publish a server, we've built a simple CLI. You can use it with:
83
+
84
+ ```bash
85
+ # Build the latest CLI
86
+ make publisher
87
+
88
+ # Use it!
89
+ ./bin/mcp-publisher --help
90
+ ```
91
+
92
+ See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
93
+
94
+ #### Other commands
95
+
96
+ ```bash
97
+ # Run lint, unit tests and integration tests
98
+ make check
99
+ ```
100
+
101
+ There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
102
+
103
+ <!--
104
+ For Claude and other AI tools: Always prefer make targets over custom commands where possible.
105
+ -->
106
+
107
+ ## Architecture
108
+
109
+ ### Project Structure
110
+
111
+ ```
112
+ ├── cmd/ # Application entry points
113
+ │ └── publisher/ # Server publishing tool
114
+ ├── data/ # Seed data
115
+ ├── deploy/ # Deployment configuration (Pulumi)
116
+ ├── docs/ # Documentation
117
+ ├── internal/ # Private application code
118
+ │ ├── api/ # HTTP handlers and routing
119
+ │ ├── auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
120
+ │ ├── config/ # Configuration management
121
+ │ ├── database/ # Data persistence (PostgreSQL)
122
+ │ ├── service/ # Business logic
123
+ │ ├── telemetry/ # Metrics and monitoring
124
+ │ └── validators/ # Input validation
125
+ ├── pkg/ # Public packages
126
+ │ ├── api/ # API types and structures
127
+ │ │ └── v0/ # Version 0 API types
128
+ │ └── model/ # Data models for server.json
129
+ ├── scripts/ # Development and testing scripts
130
+ ├── tests/ # Integration tests
131
+ └── tools/ # CLI tools and utilities
132
+ └── validate-*.sh # Schema validation tools
133
+ ```
134
+
135
+ ### Authentication
136
+
137
+ Publishing supports multiple authentication methods:
138
+ - **GitHub OAuth** - For publishing by logging into GitHub
139
+ - **GitHub OIDC** - For publishing from GitHub Actions
140
+ - **DNS verification** - For proving ownership of a domain and its subdomains
141
+ - **HTTP verification** - For proving ownership of a domain
142
+
143
+ The registry validates namespace ownership when publishing. E.g. to publish...:
144
+ - `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
145
+ - `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
146
+
147
+ ## Community Projects
148
+
149
+ Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
150
+
151
+ ## More documentation
152
+
153
+ See the [documentation](./docs) for more details if your question has not been answered here!
Binary file
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "zotero-bridge",
3
- "version": "1.0.1",
4
- "mcpName": "io.github.combjellyshen/zotero-bridge",
3
+ "version": "1.0.2",
4
+ "mcpName": "io.github.Combjellyshen/zotero-bridge",
5
5
  "description": "ZoteroBridge - MCP Server for Zotero SQLite Database Integration",
6
6
  "author": "Combjellyshen",
7
7
  "license": "MIT",
package/server.json CHANGED
@@ -1,17 +1,17 @@
1
1
  {
2
2
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
3
- "name": "io.github.combjellyshen/zotero-bridge",
4
- "description": "ZoteroBridge - MCP Server for Zotero SQLite Database Integration. Direct access to Zotero's SQLite database for collection management, tagging, PDF reading, and more.",
3
+ "name": "io.github.Combjellyshen/zotero-bridge",
4
+ "description": "MCP Server for Zotero SQLite Database - collection, tagging, PDF reading and more.",
5
5
  "repository": {
6
6
  "url": "https://github.com/Combjellyshen/ZoteroBridge",
7
7
  "source": "github"
8
8
  },
9
- "version": "1.0.1",
9
+ "version": "1.0.2",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "identifier": "zotero-bridge",
14
- "version": "1.0.1",
14
+ "version": "1.0.2",
15
15
  "transport": {
16
16
  "type": "stdio"
17
17
  }