Model Context Protocol (MCP) server for Daipendency
Connect Daipendency to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Model Context Protocol (MCP) server for Daipendency. The daipendency mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Tools — The Tools tool exposed by this serverget_dependency_docs — Extract narrative and API documentation for a dependency of a local projectInstallation goes through your MCP client rather than a global install: point it at @daipendency/mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Daipendency's toolset — Tools, get_dependency_docs — is a fair guide to whether it matches your workflow. It is maintained by chatflowdev; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Daipendency's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Tools | The Tools tool exposed by this server. |
| get_dependency_docs | Extract narrative and API documentation for a dependency of a local project. |
{
"mcpServers": {
"daipendency": {
"command": "npx",
"args": ["-y", "@daipendency/mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.