메뉴
DevOps and CI integration with microsoft/mcp (Fabric.Mcp.Server). Use when publishing packages, managing feed availability, or troubleshooting CI failures.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/microsoft/DataFactory.MCP --skill devops-fabric-mcp-integration명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | devops.fabric-mcp-integration |
| description | DevOps and CI integration with microsoft/mcp (Fabric.Mcp.Server). Use when publishing packages, managing feed availability, or troubleshooting CI failures. |
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.
The Fabric.Mcp.Server NuGet.config uses a single feed:
<packageSources>
<clear />
<add key="azure-sdk-for-net"
value="https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" />
</packageSources>
dotnet restore against the DevOps feedImportant: The
nuget listsearch index can lag behind actual availability. Ifdotnet restoresucceeds, the package IS available for CI even ifnuget listdoesn't show it yet.
nuget list Microsoft.DataFactory.MCP.Core \
-Source "https://api.nuget.org/v3/index.json" \
-PreRelease -AllVersions
Run from the microsoft/mcp repo root:
dotnet restore tools/Fabric.Mcp.Tools.DataFactory/src/Fabric.Mcp.Tools.DataFactory.csproj \
--source "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json"
If restore succeeds, the package is cached and Fabric.Mcp.Server CI will find it.
nuget list Microsoft.DataFactory.MCP.Core \
-Source "https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-net/nuget/v3/index.json" \
-PreRelease -AllVersions
The search index may lag — restore success is the definitive proof.
Version is in Directory.Build.props:
<MajorVersion>0</MajorVersion>
<MinorVersion>20</MinorVersion>
<PatchVersion>0</PatchVersion>
<PreReleaseLabel>beta</PreReleaseLabel>
Version is in Directory.Packages.props (Central Package Management):
<PackageVersion Include="Microsoft.DataFactory.MCP.Core" Version="0.20.0-beta" />
The project reference is in:
tools/Fabric.Mcp.Tools.DataFactory/src/Fabric.Mcp.Tools.DataFactory.csproj
To authenticate to the DevOps feed locally, install the credential provider: https://go.microsoft.com/fwlink/?linkid=2099625
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.
Fabric.Mcp.Server publishes with IL trimming enabled:
dotnet publish servers/Fabric.Mcp.Server/src/Fabric.Mcp.Server.csproj \
--runtime linux-x64 --self-contained \
/p:PublishTrimmed=true /p:PublishSingleFile=true /p:TreatWarningsAsErrors=true
All code consumed from Microsoft.DataFactory.MCP.Core must be trim-safe:
DataFactoryJsonContext) instead of reflection-based serialization[RequiresUnreferencedCode]| Issue | Cause | Fix |
|---|---|---|
NU1102: Unable to find package | Version not cached on DevOps feed | Run dotnet restore locally to trigger upstream cache |
nuget list doesn't show new version | Search index lag | Check with dotnet restore instead — success = available |
| 401 Unauthorized on restore | Missing credential provider | Install cred provider (link above) |
| IL2026 trim warnings on publish | Reflection-based JSON in consumed code | Use DataFactoryJsonContext source-gen JSON |