+ Hani

Implementing MCP (Model Context Protocol) servers in Document360 would be a game-changer for our customers.

MCP servers can act as a bridge between LLMs and our documentation content. This would allow customers to query our documentation in natural language and get precise answers, improving self-service and reducing support load.

It would also improve developer productivity in IDEs: With MCP integration, developers could access documentation and code examples directly in their IDE through LLM-powered assistants. This means they don’t have to leave their coding environment to search for API references or best practices—everything would be contextually available.

This feature would significantly improve developer experience and customer satisfaction.

Hi Ramesh Lokesh, D360 Product Management,

Some additional information about our use case:

MCP is essential for us for two reasons. First, it enables integrated help and contextual answers directly inside Business Central and our applications. Users can ask questions, and AI can respond based on the documentation through MCP.

However, the primary reason is far more important: MCP is a core requirement for our new AI-supported approach to software design and development. Our consultants and developers rely on AI agents that use MCP to interpret documentation, understand concepts, and align functional specifications with existing definitions in Doc360. This removes the need for consultants to manually search through documentation and eliminates avoidable inconsistencies.

If our documentation platform does not support MCP, we are forced into two unwanted options:

We are on the verge of a major shift in how we design and build our product. Without MCP support in the documentation tool, we cannot reach the required level of productivity, quality, and cost efficiency. MCP will directly reduce time spent on writing specifications and accelerate development through AI-driven workflows.

Thanks again,

Tim

Exposing a Document360 MCP server will simplify integration with AI-driven solutions compared to the existing Document360 Customer API.

It reduces backend overhead by handling complex client requests locally, instead of requiring multiple API calls to achieve the same result. Also, it avoids updates on the client side when the API specification changes.

D360 Product Management, One of our customers would like us to use an MCP server for the API Documentation content.

It would also be great if we can add MCP servers to the "Manage sources for AI assistive search" settings so Eddy can use these in any queries. We would like to include a MCP server in order to make it easier to maintain the AI search for external sources. Thanks!

We also look for MCP on docu360, we are in the process of developing ai agent, one of the things the ai agent can do is to propose an update in a article, for example, a user is having a conversation with a ai agent, the user states that the ai agent is supplying an answer (based on docu360 knowledge article) which is incorrect, the ai agent can then propose an article change by interacting with the docu360 mcp server. Of course final article modification needs to completed by a human.

Hi sergio castro, Thanks so much for the feedback. Could you please help us understand your request a bit better? It would be great if you could explain the use case in more detail—particularly what you mean by "publish as an MCP server" and how you intend AIs to access the articles. This will help us evaluate and prioritize the request more effectively. Appreciate your input!