Could you share planned date (or estimated date) for GA and non-English articles?

[wdy0719]

Could you share planned date (or estimated date) for GA and non-English articles?

[pdebruin]

Hi @wdy0719, while I am asking the GA date, you should know that Learn MCP Server reuses a number of existing services that have been around for longer https://devblogs.microsoft.com/engineering-at-microsoft/how-we-built-ask-learn-the-rag-based-knowledge-service/ and the release notes have only been about adding functionality through tools https://learn.microsoft.com/en-us/training/support/mcp-release-notes. Are you looking for something specific?

On the multi-language topic, currently the service internally works with English content since that has the biggest coverage, and agents and language models are able to translate, see my experience in Dutch
. Again :-), are you looking for something specific?

[wdy0719]

Thanks for replying. I'm specifically ask for GA date for Microsoft Learn MCP Server. As claimed in https://github.com/microsoftdocs/mcp,
the project is in Public Preview and may significantly change prior to GA:

I'm buiding AI agent may able to leverage the MCP server, and wondering if I'm giving non-english query/text to "microsoft_docs_search" - does it internally translate to English and return relevant doc/chunks in English, or in my AI agent I'll have to translate the query first(to English) before invoking 'microsoft_docs_search" tool?

[pdebruin]

I understand and my point was that the only changes have been adding MCP tools, not changing or removing.
As you can see in my screenshot, I used VS Code GitHub Copilot which took my question in Dutch, gave it to the language model which translated/analyzed it, invoked MCP, retrieved the list of results, and shaped a Dutch answer. So the idea is that the agent/LLM know about the configured MCP Servers, retrieve the latest tools, decide which MCP server to use, which MCP tool (function), what input, etc. MCP is dynamic like that. So, you should follow that patterns and have an agent with language model interface with the MCP Server. Although technically you can create code to call the Server and the Tool directly, according to the MCP specification you shouldn't. https://modelcontextprotocol.io/specification/2025-06-18/server/tools Hope that helps.

[pdebruin]

Also did you see this? #89