anchor.diff:  as part of your `ansible-playbook` command.
   
   [[local-development-only-run-the-mcp-server-locally]]
  -(Local Development Only) Run the MCP Server locally
  -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  -
  -For local development, you can run the MCP server locally instead of in
  -OpenShift. This allows for faster development feedback. To compile & run the
  +== Run the MCP Server locally (Local Development Only)
  +
  +You can run the MCP server locally instead of on
  +OpenShift. This allows for faster development feedback. To compile and run the
   MCP Server execute the following in the root directory of the repo:
   
   [source,sh]
  
positive.code: make run_server NAMESPACE=myproject
  ----
  
  As we're running the MCP Server outside of OpenShift, it won't know which project the user is in.
  The MCP Server needs to know which project so it can look for resources by namespace.
  Specifying the `NAMESPACE` var will tell MCP what project to expect resources to be in, and create a service account in that project to access resources.
  When using the MCP UI, it is important to stay within this project to avoid unusual behaviour.
  
  In another terminal, bundle the MCP UI extension for OpenShift, watching
  for changes. This is required to produce the mcp extension files
  referenced in master-config.yaml, and keep them up to date whenever
  changed during development.
  
  ....
  cd ui
  
negative.code: ----
  
  [[run-the-ansible-installer]]
  === Run the MCP Ansible Installer
  
  The installer sets up your OpenShift environment with the service catalog and the ansible service broker.
  
  [source,sh]
  ----
  