Context
The skill-creator skill explicitly recommends using microsoft-docs MCP for fresh documentation:
However, the Azure SDK language plugins currently don't have MCP configurations:
- ❌ azure-sdk-java
- ❌ azure-sdk-python
- ❌ azure-sdk-dotnet
- ❌ azure-sdk-typescript
- ❌ azure-sdk-rust
For comparison, these plugins already use MCP:
- ✅ microsoft-foundry
- ✅ azure-skills
Question
Should we add Microsoft Learn MCP to the SDK language plugin definitions?
Example for azure-sdk-java/.claude-plugin/plugin.json:
With .mcp.json:
{
"mcpServers": {
"microsoft-learn": {
"command": "npx",
"args": ["-y", "@microsoft/learn-cli@latest"]
}
}
}
Benefits
- Aligns with skill-creator guidance - Enables the "Fresh Documentation First" principle
- Prevents stale SDK info - Example: Form Recognizer rebranding could have been caught automatically
- Converges documentation efforts - Single source of truth for SDK documentation
- Consistent pattern - Same approach as microsoft-foundry plugin
Considerations
Before implementing, we should:
- Validate MS Learn docs quality - There was an exercise to ensure docs are clear and consistent, but unclear if completed
- Test the pattern - Verify that adding MCP doesn't break existing workflows
- Monitor usage - See if this becomes a recurring need across multiple SDK updates
References
Context
The skill-creator skill explicitly recommends using
microsoft-docsMCP for fresh documentation:However, the Azure SDK language plugins currently don't have MCP configurations:
For comparison, these plugins already use MCP:
Question
Should we add Microsoft Learn MCP to the SDK language plugin definitions?
Example for
azure-sdk-java/.claude-plugin/plugin.json:With
.mcp.json:{ "mcpServers": { "microsoft-learn": { "command": "npx", "args": ["-y", "@microsoft/learn-cli@latest"] } } }Benefits
Considerations
Before implementing, we should:
References
@microsoft/learn-cli(v0.1.0)