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, verifier rules, 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
get_requirements
Retrieve tenant and marketplace requirements. Supports filtering by lifecycle
status, enforcement mode, scope, and search query.
get_verifier_rules
Locate the policy-as-code verifier rules 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, verifier rule, or finding.
get_human_feedback
Read human ratings and rubric feedback for a requirement.
get_requirement_eval_suite
Zenable sees which models each repository uses and tests every requirement
against a suite of positive and negative code examples to check that the
requirement is written effectively. When the evals show room to improve,
Zenable automatically tests alternative wordings and proposes an update when
one scores higher.
This tool shows the eval suite 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.
add_requirement_eval_case
Add a code example to a requirement’s eval suite, showing code that meets
(pass) or fails to meet (violation) the requirement. Use it when the
requirement missed a real violation or flagged good code, so future scoring
catches that mistake.