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: [[local-setup]]
  Local Setup
  -----------
  
  This document will walk you through setting up a locally running Mobile
  Control Panel and a local OpenShift cluster using `oc cluster up`. This
  guide can be followed for _both_ local development and just a local
  installation.
  
  [[requirements]]
  Requirements
  ~~~~~~~~~~~~
  
  * http://docs.ansible.com/ansible/latest/intro_installation.html[Ansible]
  >= 2.3.2.0
  
negative.code: make run_server NAMESPACE=myproject
  ----
  
  When 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 allows MCP to determine which project contains required resources, 
  and to create a service account in that project to access those 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
  they are changed.
  
  ....
  cd ui
  