Skip to main content

​
Overview

The Zenable MCP (Model Context Protocol) Server enables your AI coding assistant to automatically check and improve your code against your organization’s requirements.
Your code is safe: We never retain or train on your code, regardless of tier. Read our FAQ

​
Quick Installation

The easiest way to install the Zenable MCP server is using our automated installer: 
# Install MCP server for all detected IDEs
uvx zenable-mcp install
Don’t have uvx? Install UV here
Want more features? Check out Professional or Enterprise plans to unlock advanced capabilities and increase your daily limits.
This will automatically:
  • Detect your installed IDEs
  • Configure the MCP server for each IDE
  • Install hooks where supported
  • Provide IDE-specific post-installation instructions, as needed

​
Supported IDEs

​
Full Support ✅

The following IDEs have full MCP server support. Click each for detailed installation instructions: *Continue users may experience issues until Continue adds support for streamable HTTP.

​
Enhanced Hook Support

Claude Code and Cursor have additional support for hooks, enabling advanced automation workflows like automatic code checking after file edits and intelligent context management.

​
Installation Methods

For IDE-specific installation instructions, see the individual IDE guides.
1

Install UV

Don’t have UV? Install UV here
2

Run the installer

Choose your installation scope:
# Current project only (default)
uvx zenable-mcp install

# Global installation for all projects
uvx zenable-mcp install --global
Not in a git repository? If you run the installer outside a git repository, it will discover all git repositories below your current location and present an interactive TUI for you to select which repositories to install into.

​
Post-Installation

After installation:
  1. Restart your IDE to load the new configuration
  2. Verify the connection - The Zenable MCP server should appear in your IDE’s MCP tools. You may need to manually run an authentication command to initiate the login workflow.
  3. Test the integration - Open the chat prompt and add a feature to a file, and see if recommendations appear
Need perfect consistency? While most IDEs are good at following the installed instructions, Claude Code and Cursor provide deterministic hooks that ensure reliable code checking after every file edit. These hooks are automatically configured with the same install command from above.

​
Advanced Options

​
Install for Specific IDEs

# Single IDE
uvx zenable-mcp install cursor

# Install Zenable for all supported IDEs on your system
uvx zenable-mcp install

​
Troubleshooting

Common issues and solutions:
The installer looks for IDE configuration files and installed applications. If your IDE isn’t detected:
  1. Make sure the IDE is installed
  2. Try specifying it explicitly: uvx zenable-mcp install <ide-name>
  3. Open an issue at zenable.io/feedback or email [email protected]
  1. Restart your IDE completely
  2. Check the configuration file location is correct
  3. Validate JSON syntax in the configuration file
  4. Check IDE logs for errors
The MCP server reviews files that are modified during the agent session (between prompt submit and agent stop). Some scenarios result in files not being reviewed:
  • File created then deleted: If the agent creates a temporary file and removes it before stopping, there’s nothing to review
  • File reverted to original state: If a file was modified before your prompt but the agent reverts it back to its original content, the file is no longer changed so there’s nothing new to review
  • File unchanged during session: If a file was already dirty when you submitted your prompt but the agent didn’t touch it, it won’t be reviewed
  • File created outside the workspace: Files created or modified outside the IDE’s configured workspace are not reviewed unless the IDE passes us those file paths
These are expected behaviors - the MCP server focuses on what the agent actually changed during the current session.
For complete coverage: Use GitHub or GitLab PR/MR review bots alongside MCP hooks. The server-side bots review all changes in your pull/merge request, catching anything the MCP hooks might miss.
For more detailed troubleshooting, see our troubleshooting guide.

​
Next Steps