The failure it targets is easy to reproduce: an assistant that has never seen ng-diagram reaches for hook-shaped APIs from similarly named React libraries and writes code that looks right and does not compile. search_symbols and get_symbol answer with the current signature and the exact import line, which is the part the guess gets wrong.
A documentation server for the ng-diagram Angular library. The documentation and API data ship inside the package, and both are searched then fetched — prose on one side, symbols on the other.
- The bundled documentation searched by term — guides, configuration options, examples, integration patterns — returned as matching sections — search_docs
- A whole documentation page fetched by its path when a section is not enough — get_doc
- The public API searched for classes, functions, interfaces, types, constants and enums, filterable by kind — search_symbols
- One symbol's definitive signature, its jsDoc and a ready-to-paste import statement — get_symbol
No account, no key and no network calls — the package carries the documentation and API data with it, so nothing goes stale between releases. Run npx -y @ng-diagram/mcp; on Windows launch it through cmd /c. Inside the ng-diagram monorepo, build tools/mcp-server and point the client at the built dist/index.js instead.
One command — npx -y @ng-diagram/mcp