You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fix MCP configuration format - use array instead of object
- Change from {command, args} object format to [command, flag, script] array format
- VS Code MCP installer expects array of command arguments instead of object
- Fixes 'Failed to parse scanned MCP servers: [object Object]' error
- Update all 8 installation links to use proper array format
- Should resolve VS Code MCP integration parsing issues
* Fix MCP configuration: use proper object format with type field
- Revert to {type, command, args} object format instead of array
- Include explicit 'type': 'stdio' field as required by VS Code MCP
- Fix VS Code showing 'Type: http' instead of 'stdio' in installation dialog
- Ensure proper JSON structure for VS Code MCP server configuration
- Update all 8 installation links with correct MCP server format
* fix: redesign installation to create persistent MCP configurations
- Replace temporary download-and-run URLs with proper setup approach
- Add automated setup scripts for Windows/macOS/Linux
- Provide direct download links for all platforms
- Include comprehensive manual configuration examples
- Update getting started guide with clearer troubleshooting tips
This addresses the fundamental issue where 1-click installation was creating
temporary execution commands instead of permanent .vscode/mcp.json configurations.
* docs: improve installation experience and fix linting issues
- Fix markdown linting issues (line length, emphasis as headings, bare URLs)
- Add user-level MCP server configuration option for persistent GitHub Copilot setup
- Improve readability with proper line wrapping and formatting
- Add both workspace-specific and global configuration options for flexibility
* Update README.md
Co-authored-by: Copilot <[email protected]>
* Update README.md
Co-authored-by: Copilot <[email protected]>
---------
Co-authored-by: Copilot <[email protected]>
The AKS-MCP is a Model Context Protocol (MCP) server that enables AI assistants to interact with Azure Kubernetes Service (AKS) clusters. It serves as a bridge between AI tools (like GitHub Copilot, Claude, and other MCP-compatible AI assistants) and AKS, translating natural language requests into AKS operations and returning the results in a format the AI tools can understand.
3
+
The AKS-MCP is a Model Context Protocol (MCP) server that enables AI assistants
4
+
to interact with Azure Kubernetes Service (AKS) clusters. It serves as a bridge
5
+
between AI tools (like GitHub Copilot, Claude, and other MCP-compatible AI
6
+
assistants) and AKS, translating natural language requests into AKS operations
7
+
and returning the results in a format the AI tools can understand.
4
8
5
9
It allows AI tools to:
6
10
@@ -10,11 +14,16 @@ It allows AI tools to:
10
14
11
15
## How it works
12
16
13
-
AKS-MCP connects to Azure using the Azure SDK and provides a set of tools that AI assistants can use to interact with AKS resources. It leverages the Model Context Protocol (MCP) to facilitate this communication, enabling AI tools to make API calls to Azure and interpret the responses.
17
+
AKS-MCP connects to Azure using the Azure SDK and provides a set of tools that
18
+
AI assistants can use to interact with AKS resources. It leverages the Model
19
+
Context Protocol (MCP) to facilitate this communication, enabling AI tools to
20
+
make API calls to Azure and interpret the responses.
14
21
15
22
## Available Tools
16
23
17
-
The AKS-MCP server provides consolidated tools for interacting with AKS clusters. These tools have been designed to provide comprehensive functionality through unified interfaces:
24
+
The AKS-MCP server provides consolidated tools for interacting with AKS
25
+
clusters. These tools have been designed to provide comprehensive functionality
26
+
through unified interfaces:
18
27
19
28
<details>
20
29
<summary>AKS Cluster Management</summary>
@@ -24,6 +33,7 @@ The AKS-MCP server provides consolidated tools for interacting with AKS clusters
24
33
Unified tool for managing Azure Kubernetes Service (AKS) clusters and related operations.
25
34
26
35
**Available Operations:**
36
+
27
37
-**Read-Only** (all access levels):
28
38
-`show`: Show cluster details
29
39
-`list`: List clusters in subscription/resource group
@@ -59,6 +69,7 @@ Unified tool for managing Azure Kubernetes Service (AKS) clusters and related op
59
69
Unified tool for getting Azure network resource information used by AKS clusters.
60
70
61
71
**Available Resource Types:**
72
+
62
73
-`all`: Get information about all network resources
63
74
-`vnet`: Virtual Network information
64
75
-`subnet`: Subnet information
@@ -77,21 +88,25 @@ Unified tool for getting Azure network resource information used by AKS clusters
77
88
Unified tool for Azure monitoring and diagnostics operations for AKS clusters.
78
89
79
90
**Available Operations:**
91
+
80
92
-`metrics`: List metric values for resources
81
93
-`resource_health`: Retrieve resource health events for AKS clusters
82
94
-`app_insights`: Execute KQL queries against Application Insights telemetry data
83
95
-`diagnostics`: Check if AKS cluster has diagnostic settings configured
84
-
-`control_plane_logs`: Query AKS control plane logs with safety constraints and time range validation
96
+
-`control_plane_logs`: Query AKS control plane logs with safety constraints
97
+
and time range validation
85
98
86
99
</details>
87
100
88
101
<details>
89
102
<summary>Compute Resources</summary>
90
103
91
104
**Tool:**`get_aks_vmss_info`
105
+
92
106
- Get detailed VMSS configuration for node pools in the AKS cluster
Supports both Azure Fleet management and Kubernetes ClusterResourcePlacement CRD operations.
129
+
Supports both Azure Fleet management and Kubernetes ClusterResourcePlacement
130
+
CRD operations.
114
131
115
132
</details>
116
133
117
134
<details>
118
135
<summary>Diagnostic Detectors</summary>
119
136
120
137
**Tool:**`list_detectors`
138
+
121
139
- List all available AKS cluster detectors
122
140
123
141
**Tool:**`run_detector`
142
+
124
143
- Run a specific AKS diagnostic detector
125
144
126
145
**Tool:**`run_detectors_by_category`
146
+
127
147
- Run all detectors in a specific category
128
-
-**Categories**: Best Practices, Cluster and Control Plane Availability and Performance, Connectivity Issues, Create/Upgrade/Delete and Scale, Deprecations, Identity and Security, Node Health, Storage
148
+
-**Categories**: Best Practices, Cluster and Control Plane Availability and
149
+
Performance, Connectivity Issues, Create/Upgrade/Delete and Scale,
150
+
Deprecations, Identity and Security, Node Health, Storage
129
151
130
152
</details>
131
153
@@ -137,30 +159,37 @@ Supports both Azure Fleet management and Kubernetes ClusterResourcePlacement CRD
137
159
Retrieve and manage Azure Advisor recommendations for AKS clusters.
138
160
139
161
**Available Operations:**
162
+
140
163
-`list`: List recommendations with filtering options
> **✨ Seamless Installation**: This automatically downloads the latest AKS-MCP binary from GitHub releases and configures it in VS Code. After installation, restart VS Code to activate the server.
270
+
```powershell
271
+
# Download binary and create VS Code configuration
|**Windows**| AMD64 |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22powershell%22%2C%22args%22%3A%5B%22-c%22%2C%22Invoke-WebRequest%20-Uri%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-windows-amd64.exe%20-OutFile%20aks-mcp.exe%3B%20.%2Faks-mcp.exe%20--transport%20stdio%22%5D%7D)|
224
-
|| ARM64 |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22powershell%22%2C%22args%22%3A%5B%22-c%22%2C%22Invoke-WebRequest%20-Uri%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-windows-arm64.exe%20-OutFile%20aks-mcp.exe%3B%20.%2Faks-mcp.exe%20--transport%20stdio%22%5D%7D)|
225
-
|**macOS**| Intel (AMD64) |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22bash%22%2C%22args%22%3A%5B%22-c%22%2C%22curl%20-sL%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-darwin-amd64%20-o%20aks-mcp%20%26%26%20chmod%20%2Bx%20aks-mcp%20%26%26%20.%2Faks-mcp%20--transport%20stdio%22%5D%7D)|
226
-
|| Apple Silicon (ARM64) |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22bash%22%2C%22args%22%3A%5B%22-c%22%2C%22curl%20-sL%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-darwin-arm64%20-o%20aks-mcp%20%26%26%20chmod%20%2Bx%20aks-mcp%20%26%26%20.%2Faks-mcp%20--transport%20stdio%22%5D%7D)|
227
-
|**Linux**| AMD64 |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22bash%22%2C%22args%22%3A%5B%22-c%22%2C%22curl%20-sL%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-linux-amd64%20-o%20aks-mcp%20%26%26%20chmod%20%2Bx%20aks-mcp%20%26%26%20.%2Faks-mcp%20--transport%20stdio%22%5D%7D)|
228
-
|| ARM64 |[](https://vscode.dev/redirect/mcp/install?name=AKS-MCP%20Server&config=%7B%22type%22%3A%22stdio%22%2C%22command%22%3A%22bash%22%2C%22args%22%3A%5B%22-c%22%2C%22curl%20-sL%20https%3A%2F%2Fgithub.com%2FAzure%2Faks-mcp%2Freleases%2Flatest%2Fdownload%2Faks-mcp-linux-arm64%20-o%20aks-mcp%20%26%26%20chmod%20%2Bx%20aks-mcp%20%26%26%20.%2Faks-mcp%20--transport%20stdio%22%5D%7D)|
284
+
> **✨ Simple Setup**: Download the binary for your platform, then use the manual configuration below to set up the MCP server in VS Code.
229
285
230
286
#### Manual VS Code Configuration
231
287
232
-
Alternatively, create a `.vscode/mcp.json` file in your workspace:
288
+
You can configure the AKS-MCP server in two ways:
289
+
290
+
**1. Workspace-specific configuration** (recommended for project-specific usage):
291
+
292
+
Create a `.vscode/mcp.json` file in your workspace with the path to your downloaded binary:
233
293
234
294
```json
235
295
{
236
296
"servers": {
237
297
"aks-mcp-server": {
238
298
"type": "stdio",
239
-
"command": "<path of binary aks-mcp>",
299
+
"command": "<enter the file path>",
240
300
"args": [
241
301
"--transport", "stdio"
242
302
]
@@ -245,18 +305,39 @@ Alternatively, create a `.vscode/mcp.json` file in your workspace:
245
305
}
246
306
```
247
307
248
-
#### 🚀 Getting Started with VS Code
308
+
**2. User-level configuration** (persistent across all workspaces):
309
+
310
+
For a persistent configuration that works across all your VS Code workspaces, add the MCP server to your VS Code user settings:
311
+
312
+
1. Open VS Code Settings (Ctrl+, or Cmd+,)
313
+
2. Search for "mcp" in the settings
314
+
3. Add the following to your User Settings JSON:
315
+
316
+
```json
317
+
{
318
+
"github.copilot.chat.mcp.servers": {
319
+
"aks-mcp-server": {
320
+
"type": "stdio",
321
+
"command": "<enter the file path>",
322
+
"args": [
323
+
"--transport", "stdio"
324
+
]
325
+
}
326
+
}
327
+
}
328
+
```
249
329
250
-
After installing the AKS-MCP server:
330
+
#### Step 3: Load the AKS-MCP server tools to Github Copilot
251
331
252
-
1.**Restart VS Code** - Close and reopen VS Code to load the new MCP server configuration
332
+
1. If running on an older version of VS Code: restart VS Code i.e. close and
333
+
reopen VS Code to load the new MCP server configuration.
253
334
2. Open GitHub Copilot in VS Code and [switch to Agent mode](https://code.visualstudio.com/docs/copilot/chat/chat-agent-mode)
254
-
3. Click the **Tools** button to view available tools
335
+
3. Click the **Tools** button or run /list in the Github Copilot window to see the list of available tools
255
336
4. You should see the AKS-MCP tools in the list
256
337
5. Try a prompt like: *"List all my AKS clusters in subscription xxx"*
257
338
6. The agent will automatically use AKS-MCP tools to complete your request
258
339
259
-
> **💡 Tip**: If you don't see the AKS-MCP tools after restarting, check the VS Code output panel for any MCP server connection errors.
340
+
> **💡 Tip**: If you don't see the AKS-MCP tools after restarting, check the VS Code output panel for any MCP server connection errors and verify your binary path in `.vscode/mcp.json`.
260
341
261
342
**Note**: Ensure you have authenticated with Azure CLI (`az login`) for the server to access your Azure resources.
0 commit comments