[](https://archestra.ai/mcp-catalog/opslevel__opslevel-mcp)

OpsLevel Model Context Protocol Server

This dedicated MCP (Model Context Protocol) facilitator furnishes AI agents with the requisite tooling to securely interface with and query your organization's OpsLevel repository data.

Supported Capabilities (Read-Only)

Presently, this MCP intermediary operates exclusively with read-only permissions against your OpsLevel environment, enabling retrieval of information pertaining to the following structural entities:

• Operational Procedures (Actions)
• Delivery Cycles (Campaigns)
• Quality Gates (Checks)
• Service Units (Components)
• Informational Assets (Documentation: API Specifications & Technical Documentation)
• Abstraction Layers (Domains)
• Data Scopes (Filters)
• Underlying Infrastructure References
• Code Repositories
• System Definitions
• Organizational Units (Teams)
• Personnel Identifiers (Users)

Deployment Guide

To integrate this service, follow these general stages:

1. Acquire the MCP Server Binary
2. Homebrew (macOS/Linux): Execute brew install opslevel/tap/opslevel-mcp
3. Containerization (Docker): Pull the latest image via docker pull public.ecr.aws/opslevel/mcp:latest. Consult the image registry for specific version tags.
4. Direct Download: Obtain the compiled executable for your specific OS from our official GitHub releases repository.
5. Authentication Credential Provisioning: A valid OpsLevel API Access Token must be provided to the server, typically injected via an environment variable.
6. Client Configuration: Configure the AI consumer application (e.g., Claude, VS Code) to recognize and utilize this MCP endpoint according to its specific integration format.

Integration Examples for Major Clients

For Claude (Desktop Application)

Refer to the official Claude Desktop quickstart guide for location specifics.

1. Modify the configuration file at the designated client location:
2. macOS: ${HOME}/Library/Application\ Support/Claude/claude_desktop_config.json
3. Windows: %APPDATA%\Claude\claude_desktop_config.json
4. Ensure Claude Desktop is initiated or reloaded.

Configuration snippet required within the client's MCP server map:

{ "mcpServers": { "opslevel": { "command": "opslevel-mcp", "env": { "OPSLEVEL_API_TOKEN": "XXXXXXX" } } } }

For Visual Studio Code (VS Code)

Consult the official documentation regarding MCP Servers in Copilot Chat.

1. Open Settings (Command + Comma), selecting either Workspace or User scope.
2. Navigate to Features → Chat.
3. Confirm that Mcp functionality is toggled Enabled.
4. Note: Your organization's GitHub administrator might need to activate 'preview' functionalities within Copilot settings.
5. Access the configuration via Edit in settings.json under Mcp > Discovery and incorporate the following structure (or edit the file directly):
   1. File Path (Mac OS): ${HOME}/Library/Application\ Support/Code/User/settings.json
6. Restart the VS Code instance.

Example VS Code User Settings adjustment:

{ "chat.agent.enabled": true, "chat.mcp.discovery.enabled": true, "mcp": { "inputs": [ { "type": "promptString", "id": "opslevel_token", "description": "Required OpsLevel API Authentication Key", "password": true } ], "servers": { "opslevel": { "type": "stdio", "command": "opslevel-mcp", "env": { "OPSLEVEL_API_TOKEN": "${input:opslevel_token}" } } } } }

For Cursor IDE

Reference the Cursor MCP documentation.

1. Access Cursor Settings, navigate to Settings → Cursor Settings → MCP.
2. Select the option to Add new global MCP server.
3. Insert the corresponding JSON block:

{ "mcpServers": { "opslevel": { "command": "opslevel-mcp",
"env": { "OPSLEVEL_API_TOKEN": "XXXXXX" } } } }

For Warp Terminal

1. Navigate within Warp settings to Settings > AI > Manage MCP Servers. (Alternative access routes are detailed in Warp's MCP documentation)
2. Initiate the process to Add a new server configuration.
3. Utilize the subsequent data structure:

{ "opslevel": { "command": "opslevel-mcp", "args": [], "env": { "OPSLEVEL_API_TOKEN": "XXXXXX" }, "start_on_launch": true } }

For Windsurf

1. In the Windsurf application, navigate to Settings > Advanced Settings.
2. Locate the Cascade configuration section and choose to append a new endpoint.
3. Update your local configuration file, typically named mpc_config.json (Windsurf MCP guide), using this definition:
4. Perform a Windsurf application restart.

{ "mcpServers": { "opslevel": { "command": "opslevel-mcp",
"env": { "OPSLEVEL_API_TOKEN": "XXXXXX" } } } }

Containerized Execution Override

If the binary was obtained via Docker instead of a direct installation, substitute the standard command field in the configurations above with the following Docker invocation structure:

    "command": "docker",
    "args": [
      "run",
      "-i",
      "--rm",
      "-e",
      "OPSLEVEL_API_TOKEN",
      "public.ecr.aws/opslevel/mcp:latest"
    ],

WIKIPEDIA: Cloud computing is often defined by the International Organization for Standardization (ISO) as "a paradigm for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction."

== Defining Attributes == In 2011, the United States' National Institute of Standards and Technology (NIST) established five core prerequisites for a system to qualify as 'cloud-based'. These mandatory traits are verbatim:

On-demand self-service: "A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider." Broad network access: "Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations)." Resource pooling: " The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Rapid elasticity: "Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time." Measured service: "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. By the year 2023, the ISO had issued revisions and expansions to this foundational list.

== Historical Precursors ==

The conceptual origins of cloud computing trace back to the 1960s, primarily through the widespread adoption of mainframe time-sharing techniques and Remote Job Entry (RJE). During this decade, the dominant operational pattern involved users submitting computational tasks to dedicated operations staff who executed them on centralized mainframes—the 'data center' approach. This era was characterized by intense R&D focused on maximizing the utilization of expensive, large-scale computational assets for a broader user base via efficient time-slicing. The specific graphical representation or 'cloud' metaphor for abstract, networked services was introduced in 1994 by General Magic, which applied it to illustrate the reachable 'domains' for their software agents in the Telescript architecture. This visual shorthand is attributed to communications specialist David Hoffman, drawing upon established conventions in telecommunications and network diagrams. The explicit term 'cloud computing' gained significant traction in 1996 when Compaq Computer Corporation drafted a strategic business prospectus outlining future internet-centric operations, signaling an intent to move toward software and infrastructure abstraction.