Is there an MCP resource or recommended approach to provide Copilot Agent with deeper knowledge of CommunityToolkit.MVVM?

[DevTKSS]

Is there an MCP resource or recommended approach to provide Copilot, especially the Agent with deeper knowledge of CommunityToolkit.MVVM?

I would like to extend the Copilot Agent context in Visual Studio / Visual Studio Code so that it has deeper, built-in knowledge of the CommunityToolkit.MVVM package (e.g., attributes, source generators, ObservableObject patterns, IRelayCommand, etc.).

The goal is that the agent can correctly understand the toolkit’s concepts and produce accurate suggestions that follow the recommended patterns.

Current issues

In practical use, I’ve encountered several problems where Copilot:

• seems to forget about the MVVM Toolkit entirely, even though Microsoft Docs (enabled as a resource) reference it,
• suggests removing valid and working MVVM Toolkit usage,
• or generates incorrect command implementations.

These reactions indicate that Copilot currently lacks structured knowledge of the toolkit and its design patterns.

Workaround so far

At the moment, the only viable workaround I am aware of is extensive use of a copilot-instructions.md file that manually describes the MVVM Toolkit’s concepts and expected behavior.
While this helps to some degree, it is not ideal in terms of completeness, maintainability, or accuracy.

Motivation

A dedicated MCP resource, model extension, or similar integration specifically for CommunityToolkit.MVVM would likely provide a far more reliable foundation and significantly improve Copilot’s ability to assist with MVVM Toolkit–based development.

Questions

1. Is there an existing MCP resource, model extension, or recommended approach to make Copilot Agent aware of the MVVM Toolkit’s APIs and patterns?
2. If not, would the team consider providing such a resource for use in Visual Studio / VS Code through MCP tooling or extensions?