DevOps and CI integration with microsoft/mcp (Fabric.Mcp.Server). Use when publishing packages, managing feed availability, or troubleshooting CI failures.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
DevOps and CI integration with microsoft/mcp (Fabric.Mcp.Server). Use when publishing packages, managing feed availability, or troubleshooting CI failures.
DevOps Integration with Fabric.Mcp.Server
Overview
The microsoft/mcp repo consumes Microsoft.DataFactory.MCP.Core as a NuGet package
in Fabric.Mcp.Tools.DataFactory. CI builds use a DevOps feed with upstream caching
from nuget.org — packages are not immediately available after publishing.
Feed Configuration
The Fabric.Mcp.Server NuGet.config uses a single feed:
No direct nuget.org access — all packages must come through this feed
The feed has an upstream to nuget.org that caches packages on-demand
How Upstream Caching Works
A new version is published to nuget.org
It is NOT immediately available on the DevOps feed
A Collaborator runs dotnet restore against the DevOps feed
The feed fetches and caches the package from nuget.org
Subsequent Fabric.Mcp.Server CI builds can then resolve it
Important: The nuget list search index can lag behind actual availability.
If dotnet restore succeeds, the package IS available for CI even if nuget list doesn't show it yet.
After Publishing a New Version
Step 1: Verify on nuget.org
nuget list Microsoft.DataFactory.MCP.Core \
-Source "https://api.nuget.org/v3/index.json" \
-PreRelease -AllVersions
Once installed, dotnet restore triggers an auth challenge and grants Collaborator access.
The feed is public — anyone can pull packages that are already cached.
Collaborators can also trigger the feed to ingest new packages from nuget.org.
Trim Safety Requirements
Fabric.Mcp.Server publishes with IL trimming enabled:
