Move incoming McpServer paths wholesale into Opc.Ua.Mcp folder

Upstream's master merge brought in five files that still referenced
the pre-rename 'Applications/McpServer/' path even though the actual
code (squashed commit 2784cf0) had already renamed the directory to
'Applications/Opc.Ua.Mcp/'. Realign all remaining references:

* UA Core Library.slnx — project path.
* .azurepipelines/{signlistDebug,signlistRelease}.txt — sign lists.
* .azurepipelines/preview.yml — build glob.
* .github/agents/opcua-interop-tester.agent.md — server location.
* Docs/McpServer.md — install/run snippets + architecture tree.
* Applications/Opc.Ua.Mcp/README.md — Claude / VS Code / Cursor
  config snippets + the Config.xml filename.

The runtime log path (McpServer.log.txt under %LocalApplicationData%)
is intentionally left as-is to avoid breaking existing rolling logs.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: Agent

.azurepipelines/preview.yml

@@ -84,7 +84,7 @@ jobs:
         dir /b /s Stack\Opc.Ua*.dll > .\list.txt
         dir /b /s Tools\Opc.Ua*.dll >> .\list.txt
         dir /b /s Libraries\Opc.Ua*.dll >> .\list.txt
-        dir /b /s Applications\McpServer\bin\Opc.Ua*.dll >> .\list.txt
+        dir /b /s Applications\Opc.Ua.Mcp\bin\Opc.Ua*.dll >> .\list.txt
         dir /b /s .azurepipelines\*.* >> .\list.txt
         type .\list.txt
   - task: CmdLine@2

.azurepipelines/signlistDebug.txt

@@ -78,4 +78,4 @@ Libraries\Opc.Ua.PubSub\bin\Debug\net48\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Debug\net8.0\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Debug\net9.0\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Debug\net10.0\Opc.Ua.PubSub.dll
-Applications\McpServer\bin\Debug\net10.0\Opc.Ua.Mcp.dll
+Applications\Opc.Ua.Mcp\bin\Debug\net10.0\Opc.Ua.Mcp.dll

.azurepipelines/signlistRelease.txt

@@ -78,4 +78,4 @@ Libraries\Opc.Ua.PubSub\bin\Release\net48\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Release\net8.0\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Release\net9.0\Opc.Ua.PubSub.dll
 Libraries\Opc.Ua.PubSub\bin\Release\net10.0\Opc.Ua.PubSub.dll
-Applications\McpServer\bin\Release\net10.0\Opc.Ua.Mcp.dll
+Applications\Opc.Ua.Mcp\bin\Release\net10.0\Opc.Ua.Mcp.dll

.github/agents/opcua-interop-tester.agent.md

@@ -9,7 +9,7 @@ You are an expert OPC UA interoperability test engineer. Your role is to systema
 
 ## MCP Tools — Primary Test Method
 
-This repository includes an **OPC UA MCP Server** (`Applications/McpServer`) that exposes all OPC UA Part 4 services as MCP tools. **Always prefer using the MCP tools over writing custom C# test code** — they are faster, require no compilation, and cover all standard services.
+This repository includes an **OPC UA MCP Server** (`Applications/Opc.Ua.Mcp`) that exposes all OPC UA Part 4 services as MCP tools. **Always prefer using the MCP tools over writing custom C# test code** — they are faster, require no compilation, and cover all standard services.
 
 ### When to Use MCP Tools
 - **Always** for initial connection, browsing, reading, writing, method calling, subscription testing

Applications/Opc.Ua.Mcp/README.md

@@ -36,7 +36,7 @@ Add to your `claude_desktop_config.json`:
   "mcpServers": {
     "opcua": {
       "command": "dotnet",
-      "args": ["run", "--project", "/path/to/Applications/McpServer/Opc.Ua.Mcp.csproj"]
+      "args": ["run", "--project", "/path/to/Applications/Opc.Ua.Mcp/Opc.Ua.Mcp.csproj"]
     }
   }
 }
@@ -51,7 +51,7 @@ Add to `.vscode/mcp.json`:
   "servers": {
     "opcua": {
       "command": "dotnet",
-      "args": ["run", "--project", "/path/to/Applications/McpServer/Opc.Ua.Mcp.csproj"]
+      "args": ["run", "--project", "/path/to/Applications/Opc.Ua.Mcp/Opc.Ua.Mcp.csproj"]
     }
   }
 }
@@ -107,7 +107,7 @@ Arguments:
 
 ## OPC UA Client Configuration
 
-The server uses `McpServer.Config.xml` for OPC UA client configuration, including:
+The server uses `Opc.Ua.Mcp.Config.xml` for OPC UA client configuration, including:
 
 - Application certificate settings
 - Trust list management

Docs/McpServer.md

@@ -71,15 +71,15 @@ After installation, the `opcua-mcp` command is available globally.
 ### Option 2: Run from source
 
 ```bash
-cd Applications/McpServer
+cd Applications/Opc.Ua.Mcp
 dotnet run -c Release
 ```
 
 ### Option 3: Install from local build
 
 ```bash
-dotnet pack Applications/McpServer/Opc.Ua.Mcp.csproj -c Release
-dotnet tool install --global --add-source Applications/McpServer/bin/Release OPCFoundation.NetStandard.Opc.Ua.Mcp
+dotnet pack Applications/Opc.Ua.Mcp/Opc.Ua.Mcp.csproj -c Release
+dotnet tool install --global --add-source Applications/Opc.Ua.Mcp/bin/Release OPCFoundation.NetStandard.Opc.Ua.Mcp
 ```
 
 ## Configuration
@@ -309,11 +309,11 @@ This is normal behavior — not all servers support all services. Common status
 ## Architecture
 
 ```
-Applications/McpServer/
-├── McpServer.csproj                     # .NET 10 project, packaged as dotnet tool
+Applications/Opc.Ua.Mcp/
+├── Opc.Ua.Mcp.csproj                    # .NET 10 project, packaged as dotnet tool
 ├── Program.cs                           # Entry point, stdio + HTTP/SSE transport
 ├── OpcUaSessionManager.cs               # OPC UA client session lifecycle
-├── McpServer.Config.xml                 # OPC UA client application config
+├── Opc.Ua.Mcp.Config.xml                # OPC UA client application config
 ├── .mcp/server.json                     # MCP server manifest for NuGet discovery
 ├── Tools/
 │   ├── ConnectionTools.cs               # GetEndpoints, Connect, Disconnect, GetConnectionStatus

UA Core Library.slnx

@@ -1,7 +1,7 @@
 <Solution>
   <Folder Name="/Applications/">
     <Project Path="Applications/Quickstarts.Servers/Quickstarts.Servers.csproj" />
-    <Project Path="Applications/McpServer/Opc.Ua.Mcp.csproj" />
+    <Project Path="Applications/Opc.Ua.Mcp/Opc.Ua.Mcp.csproj" />
   </Folder>
   <Folder Name="/Libraries/">
     <Project Path="Libraries/Opc.Ua.Client.ComplexTypes/Opc.Ua.Client.ComplexTypes.csproj" />