You pull up to a hotel and hand your car to the valet. You don't hand over your house keys, your garage remote, and the code to your safe. You hand over a valet key: it starts the car and opens the driver's door, and it won't open the trunk or the glove box. The valet can park the car. They can't take it on a road trip.
That's the right way to think about connecting an AI coding assistant to your DevOps tools through the Model Context Protocol (MCP). The MCP server is the valet stand. The credential you give it is the key. Almost everything that matters, what the assistant can read, what it can change, and what it can break, comes down to which key you hand over and what rules come with it. (I used AI tools to help research and draft this post, and checked the server details against each vendor's documentation.)
The valet stand: what an MCP server is
An MCP server is a small adapter that turns a tool's API into a list of actions an AI assistant can call.…