The Daipendency server allows you to extract documentation for project dependencies.
Extract Dependency Documentation: Retrieve both narrative and public API documentation for specified dependencies in local projects
Usage Requirements: Provide the dependency's name and the dependant_path (absolute path to the project)
Integration: Works with the Daipendency toolchain, utilizing TypeScript and JS bindings
The server integrates with Daipendency, which is hosted on GitHub and provides documentation extraction capabilities
Daipendency itself is implemented in Rust, though the MCP server uses TypeScript with JS bindings for Daipendency
The Daipendency MCP server is implemented in TypeScript to leverage the official MCP SDKs
Model Context Protocol (MCP) server for Daipendency.
Use npx -y @daipendency/mcp to run this MCP server with stdio.
get_dependency_docsExtract narrative and API documentation for a dependency of a local project.
This is equivalent to daipendency extract-dep.
Although Daipendency itself is implemented in Rust, this project is implemented in TypeScript so that we could use one of the official, feature-rich MCP SDKs. This required implementing JS bindings for Daipendency.
local-only server
The server can only run on the client's local machine because it depends on local resources.
Get the narrative and API documentation for the exact version of any of your dependencies. (Only Rust is supported at the moment.)
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/daipendency/daipendency-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server