internal-tool-docs-mcp
A lightweight MCP server that serves llms.txt API documentation for internal packages.
Install
pip install internal-tool-docs-mcp
Usage
Place your package documentation files in a directory, named <package-name>.txt:
docs/
├── ductile-loads.txt
├── my-other-tool.txt
Run the server:
internal-tool-docs-mcp --path ./docs
Or via uvx (no install needed):
uvx internal-tool-docs-mcp --path ./docs
Configure in .mcp.json
{
"mcpServers": {
"internal-tool-docs": {
"command": "uvx",
"args": ["internal-tool-docs-mcp", "--path", "./docs"]
}
}
}
Tools
| Tool | Description |
|---|---|
list_packages() |
List available package documentation |
get_package_docs(package_name) |
Get the llms.txt content for a package |
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for internal-tool-docs-mcp 0.1.0
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 | |
|---|---|---|---|---|
| internal_tool_docs_mcp-0.1.0.tar.gz | 47.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| internal_tool_docs_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.6 kB
Release files / internal_tool_docs_mcp-0.1.0.tar.gz
| Download URL | internal_tool_docs_mcp-0.1.0.tar.gz |
|---|---|
| Size | 47.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f69d4011fb14b0f14c44a4ba38b930eb1f07e2cf1fca0a798903f0af00456082
|
|
BLAKE2b-256 checksum How to use checksums |
c41b46234a59c8e6dd5e1cb6a9b31958e80d60d9e19dddecd3c09839ea93dda9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 2, 2026.
Transparency logRelease files / internal_tool_docs_mcp-0.1.0-py3-none-any.whl
| Download URL | internal_tool_docs_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ca36c37d8827d7be32aad72cb55e0df3d48c2b6164025f8691bc872e5417f88
|
|
BLAKE2b-256 checksum How to use checksums |
ab3ea2a84e65c6595637b3fb02cd1e417fc9eb4b1ee4eb1b5aab30f23e9537f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 2, 2026.
Transparency logSecurity for internal-tool-docs-mcp 0.1.0
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 internal_tool_docs_mcp-0.1.0.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 Mar 2, 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.
