Daipendency
Official# Daipendency MCP Server
Model Context Protocol (MCP) server for [Daipendency](https://github.com/daipendency/daipendency).
## Install
Use `npx -y @daipendency/mcp` to run this MCP server with stdio.
## API
### Tools
#### `get_dependency_docs`
Extract narrative and API documentation for a dependency of a local project.
This is equivalent to [`daipendency extract-dep`](https://github.com/daipendency/daipendency#daipendency-extract-dep-extract-the-documentation-of-a-dependency).
## Architectural Decisions
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](https://github.com/daipendency/daipendency-js).
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clear purpose focused on extracting documentation and public API for a dependency.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'dependency_docs_getter' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Daipendency', which suggests a broader scope related to dependency management. This minimal toolset feels thin and incomplete for such a domain, lacking operations like listing dependencies, checking versions, or updating dependencies.
The tool surface is severely incomplete for dependency management. While the single tool extracts documentation, there are obvious gaps: no tools to list, add, remove, or update dependencies, check for vulnerabilities, or manage version conflicts. This limits agents to a narrow, read-only task.