@azure/mcp 0.9.9 → 1.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +27 -0
  2. package/package.json +9 -9
package/README.md CHANGED
@@ -13,7 +13,12 @@ All Azure MCP tools in a single server. The Azure MCP Server implements the [MCP
13
13
  - [Documentation](#documentation)
14
14
  - [Feedback and Support](#feedback-and-support)
15
15
  - [Security](#security)
16
+ - [Permissions and Risk](#permissions-and-risk)
16
17
  - [Data Collection](#data-collection)
18
+ - [Compliance Responsibility](#compliance-responsibility)
19
+ - [Third Party Components](#third-party-components)
20
+ - [Export Control](#export-control)
21
+ - [No Warranty / Limitation of Liability](#no-warranty--limitation-of-liability)
17
22
  - [Contributing](#contributing)
18
23
  - [Code of Conduct](#code-of-conduct)
19
24
 
@@ -291,6 +296,12 @@ Your credentials are always handled securely through the official [Azure Identit
291
296
 
292
297
  MCP as a phenomenon is very novel and cutting-edge. As with all new technology standards, consider doing a security review to ensure any systems that integrate with MCP servers follow all regulations and standards your system is expected to adhere to. This includes not only the Azure MCP Server, but any MCP client/agent that you choose to implement down to the model provider.
293
298
 
299
+ You should follow Microsoft security guidance for MCP servers, including enabling Entra ID authentication, secure token management, and network isolation. Refer to [Microsoft Security Documentation](https://learn.microsoft.com/azure/api-management/secure-mcp-servers) for details.
300
+
301
+ ## Permissions and Risk
302
+
303
+ MCP clients can invoke operations based on the user’s Azure RBAC permissions. Autonomous or misconfigured clients may perform destructive actions. You should review and apply least-privilege RBAC roles and implement safeguards before deployment. Certain safeguards, such as flags to prevent destructive operations, are not standardized in the MCP specification and may not be supported by all clients.
304
+
294
305
  ## Data Collection
295
306
 
296
307
  The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft's [privacy statement](https://www.microsoft.com/privacy/privacystatement). You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.
@@ -301,6 +312,22 @@ Telemetry collection is on by default.
301
312
 
302
313
  To opt out, set the environment variable `AZURE_MCP_COLLECT_TELEMETRY` to `false` in your environment.
303
314
 
315
+ ## Compliance Responsibility
316
+
317
+ This MCP server may interact with clients and services outside Microsoft compliance boundaries. You are responsible for ensuring that any integration complies with applicable organizational, regulatory, and contractual requirements.
318
+
319
+ ## Third Party Components
320
+
321
+ This MCP server may use or depend on third party components. You are responsible for reviewing and complying with the licenses and security posture of any third-party components.
322
+
323
+ ## Export Control
324
+
325
+ Use of this software must comply with all applicable export laws and regulations, including U.S. Export Administration Regulations and local jurisdiction requirements.
326
+
327
+ ## No Warranty / Limitation of Liability
328
+
329
+ This software is provided “as is” without warranties or conditions of any kind, either express or implied. Microsoft shall not be liable for any damages arising from use, misuse, or misconfiguration of this software.
330
+
304
331
  ## Contributing
305
332
 
306
333
  We welcome contributions to the Azure MCP Server! Whether you're fixing bugs, adding new features, or improving documentation, your contributions are welcome.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@azure/mcp",
3
- "version": "0.9.9",
3
+ "version": "1.0.1",
4
4
  "description": "Azure MCP Server - Model Context Protocol implementation for Azure",
5
5
  "author": "Microsoft",
6
6
  "homepage": "https://github.com/Microsoft/mcp/blob/main/servers/Azure.Mcp.Server#readme",
@@ -14,8 +14,8 @@
14
14
  "url": "https://github.com/microsoft/mcp/issues"
15
15
  },
16
16
  "repository": {
17
- "url": "https://github.com/microsoft/mcp.git",
18
- "type": "git"
17
+ "type": "git",
18
+ "url": "https://github.com/microsoft/mcp.git"
19
19
  },
20
20
  "engines": {
21
21
  "node": ">=20.0.0"
@@ -33,12 +33,12 @@
33
33
  "arm64"
34
34
  ],
35
35
  "optionalDependencies": {
36
- "@azure/mcp-linux-arm64": "0.9.9",
37
- "@azure/mcp-win32-arm64": "0.9.9",
38
- "@azure/mcp-darwin-arm64": "0.9.9",
39
- "@azure/mcp-darwin-x64": "0.9.9",
40
- "@azure/mcp-linux-x64": "0.9.9",
41
- "@azure/mcp-win32-x64": "0.9.9"
36
+ "@azure/mcp-linux-x64": "1.0.1",
37
+ "@azure/mcp-darwin-arm64": "1.0.1",
38
+ "@azure/mcp-win32-arm64": "1.0.1",
39
+ "@azure/mcp-linux-arm64": "1.0.1",
40
+ "@azure/mcp-darwin-x64": "1.0.1",
41
+ "@azure/mcp-win32-x64": "1.0.1"
42
42
  },
43
43
  "scripts": {
44
44
  "postinstall": "node ./scripts/post-install-script.js"