Why Technical Writers Should Care About the Model Context Protocol (MCP)

Find out why making your DITA XML content AI-friendly and leveling up your skills is essential to future success

You know that feeling when you’ve just nailed a project, and someone walks in with a shiny new technology and says, “Hey, we’re doing this now!” Yeah, me too. It’s like cooking an elaborate meal only to find out your dinner guests have gone vegan. Suddenly, all your hard work feels less like a triumph and more like an impressive mistake.

Welcome to the Model Context Protocol (MCP) – the new “vegan dinner guest” of technical writing. Except this time, it’s worth your attention.

The MCP Reality Check

First, a little context (pun intended). The Model Context Protocol, or MCP, is not just some shiny new jargon. It’s an open standard developed by Anthropic. Essentially, it works to help AI models access and use data from different sources, like your carefully crafted technical documentation, in a way that doesn’t make them look like confused toddlers trying to operate a can opener.