
Qt4 Doc Mcp Server
io.github.jztan由 GitHub 账号 jztan 发布v0.7.0更新于 Oct 24, 2026
Offline MCP server for local Qt 4.8, Qt 5, and Qt 6 documentation with full-text search.
概览
一个离线 MCP 服务器,让助手搜索并阅读本地安装的 Qt 4.8、Qt 5 或 Qt 6 HTML 文档集。
- 可以做什么
- 对当前启用的 Qt 文档集做全文搜索,返回按相关性排序的结果和带高亮的片段,结果数量可配置(默认 10,最多 50)。读取转换为 Markdown 的文档页面,可只提取指定章节或对长页面分页。页面以相对于文档根目录的 Markdown 路径标识,而不是在线网址。
- 适用场景
- 适合在开发 Qt 4.8、Qt 5 或 Qt 6 代码时,让助手从本机已有的文档中查找类、函数和指南,无需联网。一次只服务一个文档集。
- 运行要求
- 本地进程,需要 Python 3.11+(或使用已发布的 Docker 镜像),并在 QT_DOC_BASE 中指定已有的 Qt HTML 文档根目录。文档、缓存和搜索索引约需 500 MB 磁盘空间,需要支持 FTS5 的 SQLite。若文档目录只读,需设置 QT_DOC_STATE_DIR。默认在 127.0.0.1:8000 上以 HTTP 运行,加参数可改用 stdio。
安装
在 SourceWeft 中
- 打开 控制台中的 Qt4 Doc Mcp Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Qt Documentation MCP Server
mcp-name: io.github.jztan/qt4-doc-mcp-server
[PyPI Version] [License] [Python Version] [GitHub Issues] [CI] [Downloads]
Bring locally installed Qt 4.8, Qt 5, or Qt 6 documentation to your AI coding assistant. Works offline with one selected documentation set at a time.
Tool Reference | Changelog | Contributing | Troubleshooting
✨ Features
- 🔌 Offline-First - Works entirely with local documentation
- 🔍 Full-Text Search - Find what you need across all Qt docs
- ⚡ Smart Caching - Fast responses for repeated queries
- 🎯 Fragment Support - Extract specific sections when needed
- 🛠️ MCP Standard - Compatible with Claude, VS Code, and other MCP clients
📦 Prerequisites
- Python 3.11+ required (not needed when using the Docker image)
- Qt HTML Documentation for one supported release (Qt 4.8, Qt 5, or Qt 6)
- The included helper downloads Qt 4.8.4 only.
- Point
QT_DOC_BASEdirectly at an existing Qt 5/6 offline documentation root.
- ~500MB disk space for docs + cache + search index
- SQLite with FTS5 support (included in Python 3.11+ by default)
🚀 Installation
From PyPI (Recommended)
From Source
Setup Qt Documentation
The helper script ships with the repo, not the PyPI package. Installed from PyPI only? Download the docs manually instead:
Then create a .env with QT_DOC_BASE pointing at that directory (see Configuration below).
Quick Start Commands
The legacy qt4-doc-mcp-server command remains available as an alias for existing client configurations.
Agent-friendly FTS CLI
After building the index, agents can search and receive materialized absolute Markdown paths:
The command reads the same .env settings as the server. Before searching, it automatically builds a missing/outdated FTS index and fully warms an incomplete Markdown cache. It then prints each result's title, absolute .md path, and FTS snippet to stdout; preparation messages, errors, and warnings go to stderr. Use qt-doc-warm-md --force after changing documentation in place.
🐳 Docker
Prebuilt multi-arch images (amd64/arm64) are published to GitHub Container Registry on every release. The container is offline-only: you mount your prepared Qt doc/html directory read-only at /docs, and all derived state (Markdown cache and search index) lives in a volume at /data.
Using only the published image, without cloning this repo? Download the Qt 4.8.4 docs directly instead of running the prepare script:
Any existing Qt 5 or Qt 6 doc/html tree (from the Qt installer or distro documentation packages) works as the mount source too.
First start converts and indexes the documentation into the /data volume; subsequent starts reuse it. Depending on the docset size, the first start can take a minute or two before the health endpoint responds.
Docker Compose
With docs in the default ./qt4-docs-html location, no configuration is needed:
For docs elsewhere (including Qt 5 or Qt 6 doc/html trees, which the server also supports), point QT_DOC_HTML_PATH at them. If port 8000 is taken on the host, set HOST_PORT in the same file (with plain docker run, change the left side of -p instead):
Or use the convenience script, which checks Docker is running, creates .env.docker on first run, builds and starts the service, and waits for the health endpoint:
Point your MCP client at http://127.0.0.1:8000/mcp (streamable HTTP). Qt documentation is licensed under GFDL 1.3; the container serves your local copy and never redistributes it.
⚙️ Configuration
These settings apply to native (pip or source) runs. In Docker they are already set inside the container (QT_DOC_BASE=/docs, QT_DOC_STATE_DIR=/data, SERVER_HOST=0.0.0.0); the QT_DOC_HTML_PATH variable in .env.docker is not a server setting, just the host path mounted at /docs.
Create a .env file in the repo root. The helper script writes sensible defaults; adjust as needed:
The tools identify documents by their exact root-relative Markdown path, not an online URL. For example, use qcompleter.md for a Qt 4 page, qtdoc/accessible.md for a Qt 5/6 global page, or qtcore/qobject.md for a Qt 5/6 Core page. By default, each docset stores its own index and Markdown cache under $QT_DOC_BASE/.index/, so switching QT_DOC_BASE reuses its existing derived state. Set QT_DOC_STATE_DIR to relocate both to a writable directory. The Markdown cache mirrors the documentation tree: for example, qtcore/qobject.md is cached as .index/md/qtcore/qobject.md plus qobject.meta.json with the default state directory.
🔌 MCP Client Setup
By default, the server exposes an HTTP endpoint at http://127.0.0.1:8000/mcp. Register it with your preferred MCP-compatible agent using the instructions below.
Stdio transport
Run the server over stdio instead of HTTP with:
For stdio-only MCP clients, configure that command with args: ["--transport", "stdio"]. Startup indexing and Markdown-cache progress are written to stderr, leaving stdout exclusively for MCP protocol messages.
Visual Studio Code (Native MCP Support)
VS Code has built-in MCP support via GitHub Copilot (requires VS Code 1.102+).
Using CLI (Quickest):
Using Command Palette:
- Open Command Palette (
Cmd/Ctrl+Shift+P) - Run
MCP: Open User Configuration(for global) orMCP: Open Workspace Folder Configuration(for project-specific) - Add the configuration:
- Save the file. VS Code will automatically load the MCP server.
Manual Configuration:
Create .vscode/mcp.json in your workspace (or mcp.json in your user profile directory):
Claude Code
Add to Claude Code using the CLI command:
Or configure manually in your Claude Code settings file (~/.claude.json):
Codex CLI
Add to Codex CLI using the command:
Or configure manually in ~/.codex/config.toml:
Note: Codex CLI primarily supports stdio-based MCP servers. The above uses mcp-client-http as a bridge for HTTP transport.
Kiro
Kiro primarily supports stdio-based MCP servers. For HTTP servers, use an HTTP-to-stdio bridge:
- Create or edit
.kiro/settings/mcp.jsonin your workspace: - Save the file and restart Kiro. The active Qt documentation tools will appear in the MCP panel.
Note: Direct HTTP transport support in Kiro is limited. The above configuration uses mcp-client-http as a bridge to connect to HTTP MCP servers.
Generic MCP Clients
Most MCP clients use a standard configuration format. For HTTP servers:
For clients that require a command-based approach with HTTP bridge:
🛠️ Available Tools
The server provides 2 MCP tools for working with the active local Qt documentation set:
-
read_documentation- Read and convert pages from the active Qt documentation set to Markdown- Fragment extraction (
#details,#public-functions) - Pagination with
start_indexandmax_length - Section-only mode for targeted content
- Returns Markdown with normalized links and GFDL attribution
- Fragment extraction (
-
search_documentation- Full-text search across the active Qt documentation set- SQLite FTS5 with BM25 relevance ranking
- Context snippets with highlighted matches
- Configurable result limits (default: 10, max: 50)
For detailed API documentation including parameters, return values, examples, and error handling, see the Tool Reference.
📚 Related Resources
- Model Context Protocol Specification
- Qt Documentation
- FastMCP Framework
- Tool Reference
- Changelog
- Contributing Guide
- Troubleshooting Guide
📄 License
- Code: MIT License (see
LICENSE). - Qt Documentation: © The Qt Company Ltd. and contributors, licensed under GFDL 1.3. This server
converts locally obtained docs and includes attribution in outputs. If you
redistribute a local mirror, include
LICENSE.FDLand preserve notices. - See
THIRD_PARTY_NOTICES.mdfor more details.
来源:README.md,提交 9998403
工具
0版本历史
1- v0.7.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分