openzim-mcp
MCP server for reading and searching ZIM archives, optimized for single-user deployments with a persistent Wikipedia archive.
README
OpenZIM MCP Server
openzim-mcp is an MCP server for reading and searching ZIM archives.
This fork keeps the same package name but is intentionally opinionated for a single-user deployment:
- bare-metal, not Docker-first
systemd-managed HTTP service- simple mode as the default operating model
- one persistent Wikipedia archive at a known path
- reduced prompt surface:
/researchonly
Current fork version: 2.0.1
Maintainer: sibyl
What This Fork Changes
Compared with upstream, this fork is optimized for a narrow and stable setup.
- simple mode still exposes
zim_query - simple mode exposes only the
/researchMCP prompt summarizeandexploreprompts are not registered- when a client mistakenly passes an entry path into
zim_file_path, simple mode treats that as a slot error and falls back to the single loaded archive
That last point matters for small models and weak MCP clients. A payload like this:
{
"compact": true,
"query": "summary of A/Marcellina_(gnostic)",
"zim_file_path": "A/Marcellina_(gnostic)"
}
now resolves against the real archive instead of treating
A/Marcellina_(gnostic) as a filesystem path.
Intended Deployment
This fork is written around a single persistent archive:
/srv/zim/wikipedia_en_all_maxi_2022-05.zim
and a local HTTP service bound to loopback, typically behind a reverse proxy.
Example service command:
uv run openzim-mcp --mode simple --transport http --host 127.0.0.1 --port 3338 /srv/zim
Features Kept In This Fork
zim_querynatural-language interface- advanced mode codepath and tooling
- HTTP transport
- search, article retrieval, structure, links, title lookup
- compact simple-mode rendering
- single registered MCP prompt:
/research
Features Intentionally De-Emphasized
- Docker-first deployment guidance
- broad multi-client prompt workflows
- prompt flows that require the caller to supply
zim_file_path
The code still contains far more capability than this README emphasizes. The difference is intentional: this document is for operating this fork, not for advertising every upstream feature.
Installation
Requirements:
- Python
3.12+ uv- a readable directory containing your
.zimfiles
Clone the repo:
git clone <your-fork-url>
cd openzim-mcp
Install dependencies:
uv sync
Run locally:
uv run openzim-mcp --mode simple /srv/zim
Run over HTTP:
uv run openzim-mcp --mode simple --transport http --host 127.0.0.1 --port 3338 /srv/zim
Bare-Metal systemd Deployment
This fork is expected to run directly on a host, not in a container.
Example unit:
[Unit]
Description=OpenZIM MCP Server
After=network-online.target
Wants=network-online.target
[Service]
User=openzim-mcp
Group=openzim-mcp
WorkingDirectory=/opt/openzim-mcp/app
EnvironmentFile=/etc/openzim-mcp/openzim-mcp.env
ExecStart=/var/lib/openzim-mcp/.local/bin/uv run openzim-mcp --mode simple --transport http --host 127.0.0.1 --port 3338 /srv/zim
Restart=always
RestartSec=5
NoNewPrivileges=true
PrivateTmp=true
ProtectSystem=strict
ProtectHome=true
ReadOnlyPaths=/srv/zim /opt/openzim-mcp
ReadWritePaths=/var/lib/openzim-mcp
RestrictSUIDSGID=true
LockPersonality=true
[Install]
WantedBy=multi-user.target
Enable it:
sudo systemctl daemon-reload
sudo systemctl enable --now openzim-mcp
sudo systemctl status openzim-mcp
Updating The Deployment
For this setup, do not copy local virtual environments into the server tree.
Deploy source only:
- copy or pull the repo into
/opt/openzim-mcp/app - keep
.venvoff the server copy - rebuild the environment on the target host with
uv sync
Typical update flow:
sudo systemctl stop openzim-mcp
cd /opt/openzim-mcp/app
git pull
sudo -u openzim-mcp /var/lib/openzim-mcp/.local/bin/uv sync
sudo systemctl start openzim-mcp
If you are deploying by copying files rather than pulling on-host, replace the whole app tree rather than pasting selected files over an existing checkout.
MCP Surface In Simple Mode
Simple mode in this fork is intentionally small.
Tools:
zim_query
Prompts:
/research/article/compare/timeline/map
That is the interface you should expect clients to see.
All prompts are workflow macros over zim_query; they do not reference the
advanced-mode tools. They assume a single offline Wikipedia archive and tell
clients to omit zim_file_path so the server can auto-select the loaded
archive.
Example Queries
These are the kinds of simple-mode requests this fork is tuned for:
tell me about Marcellinasummary of A/Marcellina_(gnostic)show structure of Photosynthesislinks in Ada Lovelacefind article titled Hypatiasearch for gnosticism
Versioning
This fork now uses a normal release version:
2.0.1
That replaces the upstream alpha train version that was present in this tree.
Development Notes
Useful commands:
uv run pytest tests/test_server.py tests/test_simple_tools.py tests/test_prompts.py -q
uv run pytest -q
The fork-specific behavior currently pinned by tests includes:
- simple mode prompt registration
- entry-like
zim_file_pathfallback in single-archive mode - reduced prompt surface
- Wikipedia-oriented simple-mode prompts over
zim_query
License
This repository remains under the existing project license unless you change it separately.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。