docs-mcp
GitHub 上の公式ドキュメントを AI が直接参照できるようにする MCP サーバーです。 登録したリポジトリのドキュメントを取り込み、Claude が「公式ドキュメントをもとに」正確に回答できるようになります。
インストール
DXT(推奨)
Claude Desktop に直接インストールできます。
- 最新リリース から
docs-mcp-<version>.dxtをダウンロード - Claude Desktop で 設定 → 拡張機能 → ファイルから追加
config.yamlのパスと OpenAI API キーを入力して完了
PyPI・Docker によるインストールは インストールガイド を参照してください。
設定
初回起動時に ~/.docs-mcp/config.yaml がテンプレートから自動生成されます。
ファイルを編集して取り込みたいリポジトリを登録します:
sources:
- id: react
url: https://github.com/reactjs/react.dev
paths:
- src/content/
embedding:
provider: openai
model: text-embedding-3-small
設定の詳細は 設定ガイド を参照してください。
使えるツール
| ツール | できること |
|---|---|
search_docs |
自然言語でドキュメントを横断検索 |
read_doc |
検索結果のページ全文を取得 |
read_sections |
特定の見出しセクションだけを取得 |
ドキュメント
開発者向け
ソースからのビルド・HTTP モード・DXT のビルド方法は 開発者向けガイド を参照してください。
ライセンス
Metadata
Release files for custom-docs-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| custom_docs_mcp-0.1.2.tar.gz | 123.1 kB | With provenance | Details for custom_docs_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| custom_docs_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for custom_docs_mcp-0.1.2-py3-none-any.whl |
Total release size: 139.9 kB
Release files / custom_docs_mcp-0.1.2.tar.gz
| Download URL | custom_docs_mcp-0.1.2.tar.gz |
|---|---|
| Size | 123.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7770ba21dacbdbc874cc1181ebf654426bc522674234587b90612b8eda268ac
|
|
BLAKE2b-256 checksum How to use checksums |
f06b3126c9990e58823bb0fc664b216b89ea240ac2e014f0bae213eff1a7c26e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 30, 2026.
Transparency logRelease files / custom_docs_mcp-0.1.2-py3-none-any.whl
| Download URL | custom_docs_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9ab7fa6f26667d3724f6c4597839bf1c80f117401f4122888e8721a39e84a85
|
|
BLAKE2b-256 checksum How to use checksums |
e62f92cb3b60155fa7a9ae728d5d2214f247b42e99ad6e432dd5d7eea6d3e2f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 30, 2026.
Transparency logSecurity for custom-docs-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for custom_docs_mcp-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.