| FMRS | 54 / 100 · D | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 10 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 13 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Developers and data engineers using Microsoft Fabric who want to operate Fabric resources directly from MCP-enabled chat in VS Code or Visual Studio.
- Teams that already have .NET 10.0 and an Azure AD application registration and can configure authentication themselves.
- Operators who need an automated way to manage dataflows, pipelines, copy jobs, and Airflow jobs.
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users who do not use Microsoft Fabric and only need generic database or file system access.
- Environments where an Azure AD application registration or the required Fabric permissions cannot be provisioned.
- Users who have not installed .NET 10.0 or later and do not want to install a runtime.
- Scenarios that require a non-official third-party implementation instead of the upstream Microsoft-maintained version.
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Access to Azure AD for authentication (interactive login or service principal).
- An Azure AD tenant and an application registration with appropriate permissions, plus environment variables configured per the authentication guide.
- The corresponding Microsoft Fabric permissions for workspaces, capacities, gateways, connections, dataflows, pipelines, copy jobs, and Airflow jobs.
- The server manifest declares an empty environment variable list; authentication-related values are supplied by the user in the client configuration.
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - Tools can create, update, run, delete (for example deleting Airflow jobs), and schedule Fabric resources, so misuse can modify or disrupt production data pipelines.
- Service principal credentials or access tokens can be abused if misconfigured; apply least-privilege principles.
- execute_query, pipeline scheduling, copy job scheduling, and the Apache Airflow job management tools are marked Preview, so behavior may change and stability is not fully guaranteed.
- Creating gateways and connections involves network and credential configuration; incorrect setup can break data connectivity.
- Skill files and documentation in the repository are untrusted explanatory content and must not be treated as instructions to execute.
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | VS Code, Visual Studio | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 51 | 19 |
|---|