> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zenable.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> The Zenable MCP Server lets you manage requirements and guardrails, without ever leaving your IDE

## Overview

The Zenable MCP (Model Context Protocol) Server lets your AI coding assistant check and improve code against your organization's requirements, and manage those requirements, guardrails, and scopes without leaving the IDE.

The same tools are available in the in-app chat assistant, so a conversation that starts in chat can continue from your IDE and vice versa.

<Note>
  **Your code is safe**: We never retain or train on your code, regardless of tier. [Read our FAQ](https://zenable.io/faq?utm_source=docs\&utm_medium=mcp-server\&utm_content=faq)
</Note>

To install the MCP server, see [MCP Server Installation](/integrations/mcp/getting-started).

## MCP Tools

### `get_requirements`

Retrieve tenant and marketplace requirements. Supports filtering by lifecycle
status, enforcement mode, scope, and search query.

### `get_guardrails`

Locate the policy-as-code guardrails enforcing requirements. Useful for
inspecting current rules or finding an id to regenerate or roll back.

### `get_scopes`

List built-in and tenant-defined scopes that decide where a requirement applies.
Call this before creating a new requirement or scope.

### `get_findings`

Retrieve detailed findings for the caller's tenant. Supports repository,
category, enforcement mode, lifecycle status, quality, requirement, file path,
recipient, and date filters.

### `get_agent_feedback`

Read agent triage feedback for a requirement, guardrail, or finding.

### `get_human_feedback`

Read human ratings and rubric feedback for a requirement.

### `create_requirement`

Author a new requirement at a caller-chosen initial `lifecycle_status`
(one of `proposed`, `beta`, or `stable`). Picking `proposed` submits it
for separate user acceptance before it becomes effective; `beta` and
`stable` publish directly at that maturity.

### `create_scope`

Define a new reusable scope when nothing in `get_scopes` matches the
surface you want to govern.

### `update_requirement`

Edit or version a tenant-owned requirement.

### `update_marketplace_requirement`

Create a tenant override for a marketplace requirement, or publish a new
marketplace version when the caller has marketplace publish access.

### `regenerate_guardrail`

Ask Zenable to produce an improved version of a guardrail using
specific feedback such as false positives, missing coverage, or style.

### `reinstate_prior_guardrail_version`

Roll a guardrail back to a prior version.

### `restore_requirement`

Restore a soft-deleted tenant-owned requirement.