Skip to content

Add Microsoft Learn MCP to Azure SDK language plugins #293

@samvaity

Description

@samvaity

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

  1. Aligns with skill-creator guidance - Enables the "Fresh Documentation First" principle
  2. Prevents stale SDK info - Example: Form Recognizer rebranding could have been caught automatically
  3. Converges documentation efforts - Single source of truth for SDK documentation
  4. Consistent pattern - Same approach as microsoft-foundry plugin

Considerations

Before implementing, we should:

  1. Validate MS Learn docs quality - There was an exercise to ensure docs are clear and consistent, but unclear if completed
  2. Test the pattern - Verify that adding MCP doesn't break existing workflows
  3. Monitor usage - See if this becomes a recurring need across multiple SDK updates

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions