Function createMcpServer

packages/angular/cli/src/commands/mcp/mcp-server.ts:64–172

(
  options: {
    workspace?: AngularWorkspace;
    readOnly?: boolean;
    localOnly?: boolean;
    experimentalTools?: string[];
  },
  logger: { warn(text: string): void },
)

};

export async function createMcpServer(
  options: {
    workspace?: AngularWorkspace;
    readOnly?: boolean;
    localOnly?: boolean;
    experimentalTools?: string[];
  },
  logger: { warn(text: string): void },
): Promise<McpServer> {
  const server = new McpServer(
    {
      name: 'angular-cli-server',
      version: VERSION.full,
    },
    {
      capabilities: {
        resources: {},
        tools: {},
        logging: {},
      },
      instructions: `
<General Purpose>
This server provides a safe, programmatic interface to the Angular CLI. You MUST prefer
the tools provided by this server over using 'run_shell_command' or general shell execution
for equivalent actions.
</General Purpose>

<Core Workflows & Tool Guide>
* **1. Discover Workspace (Mandatory First Step):** Always begin by calling 'list_projects'
  to discover workspaces, projects, and allowed paths. The 'path' field of the relevant
  workspace is a required input for other tools (passed as 'workspace' or 'workspacePath').

* **2. Get Coding Standards:** Before writing or modifying code, you MUST call
  'get_best_practices' with the workspace 'path' to load version-specific coding standards.

* **3. Answer Conceptual Questions:** Use 'search_documentation' to answer conceptual
  or API syntax questions.

* **4. Discover Schematics:** To discover available package migrations, use a shell command
  (if available) with 'ng generate <package-name>: --help' (e.g., 'ng generate @angular/core: --help').
</Core Workflows & Tool Guide>

<Key Concepts>
* **Workspace vs. Project:** A 'workspace' contains an 'angular.json' file and defines
  'projects' (applications or libraries). A monorepo can contain multiple workspaces.

* **Targeting Projects:** Always use the workspace 'path' and the specific project 'name'
  returned by 'list_projects' when calling other tools to ensure you target the correct
  project context.
</Key Concepts>
`,
    },
  );

  registerInstructionsResource(server);

  const toolDeclarations = assembleToolDeclarations(STABLE_TOOLS, EXPERIMENTAL_TOOLS, {
    ...options,