@microsoft/powerbi-modeling-mcp-linux-arm64 0.5.0-beta.15 → 0.5.0-beta.16

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 The Power BI Authoring MCP Server is a multiplatform application that updates automatically in internal flows. Updates will be released periodically.
 
+## [0.5.0-beta.16] - 2026-09-24 - Pre-release
+
+### Features
+
+- Update --accept-eula behavior and rename local application folder, with automatic migration
+
+### Other Changes
+
+- Document custom XMLA endpoint allowlisting and access token trust
+
 ## [0.5.0-beta.15] - 2026-09-24 - Pre-release
 
 ### Fixes
@@ -26,7 +36,7 @@ The Power BI Authoring MCP Server is a multiplatform application that updates au
 
 ### Security 🛡️
 
-- *(mcp)* Add durable local audit logging
+- Add durable local audit logging
 
 ## [0.5.0-beta.13] - 2026-08-27 - Pre-release
 

package/README.md

@@ -55,10 +55,11 @@ Configure the `mcp.json` file with the following:
 
 ## License
 
-Before use, you must accept the Power BI Authoring MCP End User License Agreement at **<https://github.com/microsoft/powerbi-modeling-mcp>**. To accept:
+Before use, you must accept the Power BI Authoring MCP End User License Agreement at **<https://go.microsoft.com/fwlink/?LinkId=2381247>**. To accept:
 
 1. **Command line**: pass `--accept-eula` (or the alias `--accepteula`, case-insensitive) when
-   starting the server. This also persists acceptance.
+   starting the server. This grants acceptance for
+   the current process only and does **not** persist anything to disk.
 2. **Environment variable**: set `PBI_MODELING_MCP_ACCEPT_EULA=true`. This grants acceptance for
    the current process only and does **not** persist anything to disk.
 3. **The `accept_eula` MCP tool**: an MCP client can call `accept_eula` with the required
@@ -92,7 +93,7 @@ Once the connection is established, you can use natural language to ask the AI a
 
 The local MCP writes audit events to daily newline-delimited JSON
 files. On Windows, the default directory is
-`%LOCALAPPDATA%\Microsoft\PowerBI Authoring\Logs`. These files contain audit
+`%LOCALAPPDATA%\Microsoft\powerbi-authoring-mcp\Logs`. These files contain audit
 metadata and do not include general console or diagnostic logs. Tenant, user,
 and network request fields are omitted.
 
@@ -112,6 +113,18 @@ startup. Apply appropriate file protection to the directory.
 
 Your credentials are always handled securely through the official [Azure Identity SDK](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/identity/Azure.Identity/README.md) - **we never store or manage tokens directly**.
 
+### Custom XMLA endpoints
+
+Organizations that need to connect the local MCP server to custom Analysis Services or Power BI XMLA endpoints can allowlist those endpoint hosts. This configuration is intended for users or administrators who control the MCP server configuration and have verified that the endpoints are trusted by their organization.
+
+By default, outbound Analysis Services connections are limited to localhost and the configured Fabric host. To allow additional endpoint hosts, set a comma-separated list before starting the server:
+
+```powershell
+$env:PBI_MODELING_MCP_ALLOWED_CONNECTION_HOSTS = "server1.contoso.com,server2.contoso.com"
+```
+
+Access tokens will be passed to the hosts configured in `PBI_MODELING_MCP_ALLOWED_CONNECTION_HOSTS`. Users should therefore be cautious when adding hosts and only include hosts that their organization trusts and intends to use as Analysis Services or Power BI XMLA endpoints.
+
 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 Power BI Authoring MCP Server, but any MCP client/agent that you choose to implement down to the model provider.
 
 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/en-us/azure/api-management/secure-mcp-servers) for details.

package/dist/Resources/tools/tool-metadata.override.yaml

@@ -1,7 +1,7 @@
 tools:
   accept_eula:
     description: >-
-      Accepts the Power BI Authoring MCP End User License Agreement (EULA) at https://github.com/microsoft/powerbi-modeling-mcp. This tool must not be called automatically or speculatively by an AI agent. Only call it after a human user has reviewed the EULA at that URL and explicitly instructed you to accept it on their behalf.
+      Accepts the Power BI Authoring MCP End User License Agreement (EULA) at https://go.microsoft.com/fwlink/?LinkId=2381247. This tool must not be called automatically or speculatively by an AI agent. Only call it after a human user has reviewed the EULA at that URL and explicitly instructed you to accept it on their behalf.
     request:
       EulaUrl: >-
-        The exact EULA URL the user reviewed. Must be https://github.com/microsoft/powerbi-modeling-mcp
+        The exact EULA URL the user reviewed. Must be https://go.microsoft.com/fwlink/?LinkId=2381247

package/dist/powerbi-modeling-mcp

@@ -1,4 +1,4 @@
 [diffend] Oversized file quarantined before diffing.
 name: package/dist/powerbi-modeling-mcp
-size: 39036252 bytes
-sha256: 68be06400fbb64550077c640abc9b9b20240adf2baa3e57ca86859e61c7750a8
+size: 39052087 bytes
+sha256: 4df926a2dc110b459742227ae94274f1b7bd3c694317be063d7e9c7e4506d750

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@microsoft/powerbi-modeling-mcp-linux-arm64",
-  "version": "0.5.0-beta.15",
+  "version": "0.5.0-beta.16",
   "description": "Power BI Authoring MCP Server - Node.js client packaging to author Power BI semantic models in Power BI Desktop, Microsoft Fabric workspaces, and local PBIP and TMDL files., for linux on arm64",
   "author": "Microsoft",
   "homepage": "https://github.com/microsoft/powerbi-modeling-mcp#readme",