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.Your code is safe: We never retain or train on your code, regardless of tier. Read our FAQ
MCP Tools
search_marketplace_requirements
Retrieve requirements from the Zenable marketplace that are enabled for
your environment.
search_requirements
Retrieve the requirements from your tenant. Supports filtering by
lifecycle status, so you can narrow to draft, beta, stable, deprecated,
archived, or declined requirements.
search_guardrails
Locate the policy-as-code guardrails enforcing a requirement. Useful
for inspecting the current rule, or grabbing an id to regenerate or
roll back.
list_scopes
List the scopes, both built-in and tenant-defined, that decide where
a requirement applies. Call this before creating a new requirement or
scope.
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 list_scopes matches the
surface you want to govern.