DevOps Loop MCP server

The DevOps Loop Model Context Protocol (MCP) server provides a standardized interface so that external MCP clients can interact with DevOps Loop and perform supported operations.

The MCP-compatible clients, such as Visual Studio Code (through MCP extensions) and Claude Desktop, can use this interface to query, retrieve, and modify loop resources directly from their development or AI-assisted environments.

By using the MCP server, you can access DevOps Loop capabilities without switching between interfaces. It enforces secure and controlled access by honoring the permissions defined in DevOps Loop.

The server maintains session security through a 30-minute idle timeout. If no activity occurs during this period, the session expires and requires reauthentication. After initial configuration, MCP client settings are stored persistently. MCP clients then reconnect automatically in subsequent sessions.

The MCP server offers a set of domain-specific tools that allow external clients to perform the following operations:

  • Managing loops

  • Accessing tenant and teamspace information

  • Querying analytics data

  • Performing deployment and build operations

  • Managing repositories and pull requests

  • Interacting with planning and test resources

Each tool defines its required inputs and expected outputs, ensuring consistent and predictable interactions.