Skip to main content
Documentation access gives your agent a direct way to inspect package docs without leaving the coding session. GitHits covers both hosted documentation and documentation files backed by repositories. Use these tools when docs explain the public API better than source code, or when your agent needs to compare documented behavior against implementation behavior.
docs_list lists available documentation pages for a package. It covers hosted/crawled docs and repository-backed documentation files.Every entry includes a stable pageId, a sourceKind (crawled or repo), and a source URL. Repository-backed entries also expose repoUrl, gitRef, and filePath for source follow-ups.CLI usage
npx githits@latest docs list npm:express
npx githits@latest docs list pypi:requests --limit 20
Parameters
​
registry
string
required
Package registry.
​
package_name
string
required
Package name. Scoped names are supported.
​
version
string
Optional package version.
​
limit
number
Maximum pages to return (1-500, default 100).
docs_read reads a single documentation page by its pageId. Pass the pageId returned by docs_list or from a search result.Use start_line and end_line to fetch a slice of a long page. The response carries totalLines so the agent can continue reading the next slice when needed.CLI usage
npx githits@latest docs read <pageId>
npx githits@latest docs read <pageId> --start-line 50 --end-line 150
Parameters
​
page_id
string
required
Documentation page ID from docs_list or search results.
​
start_line
number
Starting line (1-indexed). Omit for the full page.
​
end_line
number
Ending line (inclusive). Omit for end of page.

​
MCP tool reference

MCP toolCLI commandPurpose
docs_listnpx githits@latest docs listBrowse documentation pages for a package
docs_readnpx githits@latest docs readRead a documentation page by page ID