Developer-tools MCP server
Angular CLI MCP
Version history of discovered tools, schemas, and declared agent authority.
OBSERVED INTERFACE
Capability surface
Modelara’s observed declarations are shown separately from its derived effect classifications.
- 6
- 3
- 0
- 0
Unknown means Valyd could not determine the capability's effect confidently from the declared interface and static evidence. It is not treated as safe.
- Package
- @angular/cli@22.2.7
- Registry
- npm
- Published
- Nov 12, 2026
- Integrity
sha512-TtO2qiDJj3OjeqZ1V/SiDYkwBKDVk45PxDBxjNksw5sLe2H122RYjdcVPDteEGJjAJGwnP2qkQ5wa/6YRitNiA==- Analyzer
- modelara v0.1.8 · policy not recorded
- Repository
- https://github.com/angular/angular-cli
9 capabilities
| Capability | Type | Derived effect | First observed in Valyd coverage | Last changed |
|---|---|---|---|---|
ai_tutorangular-cli:tool:ai_tutorObserved interface and hashes<Purpose> Loads the core instructions, curriculum, and persona for the Angular AI Tutor. This tool acts as a RAG (Retrieval-Augmented Generation) source, effectively reprogramming the assistant to become a specialized Angular tutor by providing it with a new core identity and knowledge base. </Purpose> <Use Cases> * The user asks to start a guided, step-by-step tutorial for learning Angular (e.g., "teach me Angular," "start the tutorial"). * The user asks to resume a previous tutoring session. </Use Cases> <Operational Notes> * The text returned by this tool is a new set of instructions and rules for you, the LLM. It is NOT meant to be displayed to the user. * After invoking this tool, you MUST adopt the persona of the Angular AI Tutor and follow the curriculum provided in the text. * Be aware that the tutor persona supports special user commands, such as "skip this section," "show the table of contents," or "set my experience level to beginner." The curriculum text will provide the full details on how to handle these. * Your subsequent responses should be governed by these new instructions, leading the user through the "Smart Recipe Box" application tutorial. * As the tutor, you will use your other tools to access the user's project files to verify their solutions as instructed by the curriculum. </Operational Notes> Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
devserver_startangular-cli:tool:devserver_startObserved interface and hashes<Purpose> Starts the Angular development server ("ng serve") as a background process. Follow this up with "devserver_wait_for_build" to wait until the first build completes. </Purpose> <Use Cases> * **Starting the Server:** Use this tool to begin serving the application. The tool will return immediately while the server runs in the background. * **Get Initial Build Logs:** Once a dev server has started, use the "devserver_wait_for_build" tool to ensure it's alive. If there are any build errors, "devserver_wait_for_build" would provide them back and you can give them to the user or rely on them to propose a fix. * **Get Updated Build Logs:** Important: as long as a devserver is alive (i.e. "devserver_stop" wasn't called), after every time you make a change to the workspace, re-run "devserver_wait_for_build" to see whether the change was successfully built and wait for the devserver to be updated. </Use Cases> <Operational Notes> * This tool manages development servers by itself. It maintains at most a single dev server instance for each project in the monorepo. * This is an asynchronous operation. Subsequent commands can be ran while the server is active. * Use 'devserver_stop' to gracefully shut down the server and access the full log output. * **Keeping the Server Alive**: It is often better to keep the server alive between tool calls if you expect the user to request more changes or run more tests, as it saves time on restarts and maintains the file watcher state. You must still call 'devserver_wait_for_build' after every change to see whether the change was successfully built and be sure that the app was updated. * **Consistent Ports**: If making multiple calls, it is recommended to reuse the port you got from the first call for subsequent ones. </Operational Notes> Input schemasha256:99d665177de9c47ec8e727ac19df475fdb4d0d20ec741b9e7700a30e9aa20306Output schemasha256:b41a16d6376a96574ea9d582013058a0cd69e6aabbec2ddfe84d70171c3f93ccDescription hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
devserver_stopangular-cli:tool:devserver_stopObserved interface and hashes<Purpose> Stops a running Angular development server ("ng serve") that was started with the "devserver_start" tool. </Purpose> <Use Cases> * **Stopping the Server:** Use this tool to terminate a running development server and retrieve the logs. </Use Cases> <Operational Notes> * This should be called to gracefully shut down the server and access the full log output. * This just sends a SIGTERM to the server and returns immediately; so the server might still be functional for a short time after this is called. However note that this is not a blocker for starting a new devserver. </Operational Notes> Input schemasha256:c31a38e73150031d84c583340b903499694eb69397c0c9d6178ae21ad9b3ed0eOutput schemasha256:ebe8357f3c2e7e595be2a90fb96f7714bd31ea61336f0012d51a82c72fbe7815Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
devserver_wait_for_buildangular-cli:tool:devserver_wait_for_buildObserved interface and hashes<Purpose> Waits for a dev server that was started with the "devserver_start" tool to complete its build, then reports the build logs from its most recent build. </Purpose> <Use Cases> * **Waiting for a build:** As long as a devserver is alive ("devserver_start" was called for this project and "devserver_stop" wasn't called yet), then if you're making a file change and want to ensure it was successfully built, call this tool instead of any other build tool or command. When it retuns you'll get build logs back **and** you'll know the user's devserver is up-to-date with the latest changes. </Use Cases> <Operational Notes> * This tool expects that a dev server was launched on the same project with the "devserver_start" tool, otherwise the tool will fail. * This tool will block until the build is complete or the timeout is reached. If you expect a long build process, consider increasing the timeout. Timeouts on initial run (right after "devserver_start" calls) or after a big change are not necessarily indicative of an error. * If you encountered a timeout and it might be reasonable, just call this tool again. * If the dev server is not building, it will return quickly, with the logs from the last build. </Operational Notes> Input schemasha256:edd5298834488751e38f8cd5eebe5626686dd1b2ac3ac8afc5076331a6a1217aOutput schemasha256:b858dbe328d18a7bde432e807dee4c0075e3e537256130158c90bdfe53409c55Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
get_best_practicesangular-cli:tool:get_best_practicesObserved interface and hashes<Purpose> Retrieves the official Angular Best Practices Guide. This guide contains the essential rules and conventions that must be followed for any task involving the creation, analysis, or modification of Angular code. </Purpose> <Use Cases> * Mandatory first step before writing or modifying Angular code to ensure modern framework standards. * Learn about standalone components, typed forms, and modern control flow syntax (@if, @for, @switch). * Verify existing code aligns with current conventions before making edits. </Use Cases> <Operational Notes> * Provide the 'workspacePath' argument (obtained via 'list_projects') to load the version-specific guide matching the project's Angular framework. * Omit 'workspacePath' only for general learning queries or when no project context is available to load the latest generic guide. </Operational Notes> Input schemasha256:d85e2f247a39dd45d40b9c2864bf11cccfaecafbe34dbeb5ba2233ecf6b874a7Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
list_projectsangular-cli:tool:list_projectsObserved interface and hashes<Purpose> Provides a comprehensive overview of all Angular workspaces, projects, and configured targets within the repository. Always use this tool as a mandatory first step before performing any project-specific actions to understand the available projects and locations. </Purpose> <Use Cases> * Discovering project names, locations, builders, selector prefixes, and style languages before generating or building components. * Determining a project's unit test framework (Jasmine, Jest, or Vitest) before writing or modifying tests. * Identifying available execution targets (e.g., lint, e2e, serve, deploy) before attempting execution. * Disambiguating multiple workspaces in monorepos. </Use Cases> <Operational Notes> * Execute shell/CLI commands from the parent directory of the workspace's 'path' field. * If 'unitTestFramework' is 'unknown', inspect local config files (e.g., jest.config.js, karma.conf.js) or the 'test' target in 'angular.json' to determine the framework before creating tests. </Operational Notes> Input schemasha256:3178d649f32f96ea850da50c27c062f5c20cbef86dec2f5af0587dff56ebdb67Output schemasha256:ed20a1d4bdb6f6ee2a2b7035fbb7f9f94432dd551b19d7534ebcafc8e5560cbeDescription hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
onpush_zoneless_migrationangular-cli:tool:onpush_zoneless_migrationObserved interface and hashes<Purpose> Analyzes Angular code and provides a step-by-step, iterative plan to migrate it to 'OnPush' change detection (a prerequisite for zoneless applications). </Purpose> <Use Cases> * Generating component-specific migrations from default change detection to OnPush. * Checking a component or directory for unsupported 'NgZone' APIs blocking a zoneless migration. * Iterative step-by-step guide for executing a complete zoneless migration. </Use Cases> <Operational Notes> * This tool is strictly read-only and does NOT modify code. It outputs EXACTLY ONE actionable step at a time. * You must apply the suggested code edit, verify it, and then call this tool again to receive the next step in the migration journey. * Run modernization schematics (e.g., Signal Inputs migrations) as prerequisites before starting this migration. * Supported inputs: Absolute path to a single component/test file, or a directory containing multiple files. </Operational Notes> Input schemasha256:bc5b73a4dcb1b1327143238ae3eebca5e1fa02436abad2790d6cbda372d6ab70Output schemaNot exposed in the analyzed interface. sha256:398b676e47d03a29016ee92fe378b8b4f1b3e965390c4c64ce78d27f79df74d1Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
run_targetangular-cli:tool:run_targetObserved interface and hashes<Purpose> Executes a configured target (such as build, test, lint, e2e) for an Angular project. This is the single, unified interface for executing all project tasks natively. </Purpose> <Use Cases> * Building an application or library. * Running unit tests, E2E tests, or linters. * Deploying or running custom workspace targets discovered via 'list_projects'. </Use Cases> <Operational Notes> * Mandatory Discovery: You MUST discover available project targets by calling 'list_projects' first. * Headless Testing: For official builders, the test target automatically runs in headless mode and disables watch mode to guarantee clean execution. * Output Paths: For official builders, successful builds return the build directory in 'outputPath' under the extensions metadata. * Watch mode (serve target or watch options) is NOT yet supported in this version of run_target. You MUST use the legacy 'devserver_*' tools for background server lifecycles. </Operational Notes> Input schemasha256:edba28a9c6eb830b2bf8afe0c34082e72551e7159ef6e63c26685a2d9b8138eaOutput schemasha256:c9946623a12152308ec69f8ba8f7508479dd1f1dbf4f909f9da6db861b0531d0Description hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed | |
search_documentationangular-cli:tool:search_documentationObserved interface and hashes<Purpose> Searches the official Angular documentation (angular.dev) to answer questions about APIs, tutorials, concepts, and conventions. </Purpose> <Use Cases> * Answering questions about Angular concepts (e.g., standalone components). * Finding correct API signatures or syntax (e.g., ngFor trackBy). * Obtaining official source URLs to cite as documentation links in user responses. </Use Cases> <Operational Notes> * Provide the major Angular version in the 'version' parameter (obtained from 'frameworkVersion' in 'list_projects' or from 'ng version') to ensure version-aligned results. * Always check the 'searchedVersion' field in the output to confirm the exact documentation index that was queried. * For best results, provide a concise keyword query (e.g., "NgModule") rather than a natural language sentence. </Operational Notes> Input schemasha256:a850445c877927604624e6eba46bf4334864c19994c6f0b1cac5face89392679Output schemasha256:4266df93ce2e1bb69e4876d3a68b28d33d414e02aa8fb80fa667bcc06e2f63bcDescription hash: Interface hash: Other observed Modelara metadata | tool | 22.2.5 | No change observed |
No capabilities match these filters.
STATIC COMPARISONS
Release history
- 22.2.6 22.2.7PASS0 added0 removed0 schema0 write0 destructive0 unknown
- 22.2.5 22.2.6PASS0 added0 removed0 schema0 write0 destructive0 unknown