> ## 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 Installation

> Set up the Zenable MCP Server in your IDE using our automated installer

## 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.

<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-getting-started\&utm_content=faq)
</Note>

## Quick Installation

The easiest way to install the Zenable MCP server is using our automated installer:

```bash theme={null}
# Install MCP server for all detected IDEs
zenable install
```

<Note>
  Don't have the Zenable CLI? Install it first:

  <CodeGroup>
    ```bash macOS / Linux theme={null}
    curl -fsSL https://cli.zenable.app/install.sh | bash
    ```

    ```powershell Windows theme={null}
    powershell -ExecutionPolicy Bypass -Command "irm https://cli.zenable.app/install.ps1 | iex"
    ```
  </CodeGroup>
</Note>

<Note>
  **Want more features?** Check out [Professional](https://zenable.io/pricing?tier=pro\&utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=pricing-pro) or [Enterprise](https://zenable.io/pricing?tier=enterprise\&utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=pricing-enterprise) plans to unlock [advanced capabilities](https://zenable.io/pricing?tier=pro\&utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=pro-features) and increase your daily limits.
</Note>

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:

* **[Amp](/integrations/mcp/ide/amp)**
* **[Cursor](/integrations/mcp/ide/cursor)**
* **[Claude Code](/integrations/mcp/ide/claude-code)**
* **[Codex](/integrations/mcp/ide/codex)**
* **[Continue](/integrations/mcp/ide/continue)**\*
* **[GitHub Copilot CLI](/integrations/mcp/ide/copilot)**
* **[Windsurf](/integrations/mcp/ide/windsurf)**
* **[Gemini CLI](/integrations/mcp/ide/gemini)**
* **[Kiro](/integrations/mcp/ide/kiro)**
* **[Roo Code](/integrations/mcp/ide/roo)**
* **[VS Code](/integrations/mcp/ide/vscode)**
* **[Antigravity](/integrations/mcp/ide/antigravity)**
* **[Auggie](/integrations/mcp/ide/auggie)**
* **[Cline](/integrations/mcp/ide/cline)**
* **[OpenCode](/integrations/mcp/ide/opencode)**

\*Continue users may experience issues until Continue adds [support for streamable HTTP](https://github.com/continuedev/continue/issues/6282).

### Enhanced Hook Support

**[Claude Code](/integrations/mcp/ide/claude-code)**, **[Cursor](/integrations/mcp/ide/cursor)**, **[Windsurf](/integrations/mcp/ide/windsurf)**, **[Kiro](/integrations/mcp/ide/kiro)**, **[Auggie](/integrations/mcp/ide/auggie)**, **[Cline](/integrations/mcp/ide/cline)**, and **[OpenCode](/integrations/mcp/ide/opencode)** (via its plugin system) have additional support for hooks, enabling advanced automation workflows like automatic code checking after file edits and intelligent context management.

**[Codex](/integrations/mcp/ide/codex)** has limited hook support (session start and stop only as of 2026-03-11).

## Installation Methods

For IDE-specific installation instructions, see the [individual IDE guides](/integrations/mcp/getting-started#supported-ides).

### Method 1: Automated Installation (Recommended)

<Steps>
  <Step title="Run the installer">
    ```bash theme={null}
    # Install globally for all projects (default)
    zenable install
    ```

    This makes Zenable available across all your projects.

    <Note>
      **Want project-level installation?** Run `zenable install --project` from inside a git repository to install only for that project.
    </Note>
  </Step>
</Steps>

## 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

<Tip>
  **Need perfect consistency?** While most IDEs are good at following the installed instructions, Claude Code, Cursor, Windsurf, Kiro, Auggie, Cline, and OpenCode provide
  deterministic hooks that ensure reliable code checking after every file edit. These hooks are automatically configured with the same `install` command from above.
</Tip>

## Advanced Options

### Install for Specific IDEs

```bash theme={null}
# Single IDE
zenable install cursor

# Install Zenable for all supported IDEs on your system
zenable install
```

## Troubleshooting

Common issues and solutions:

<AccordionGroup>
  <Accordion title="IDE not detected">
    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: `zenable install <ide-name>`
    3. Open an issue at [zenable.io/feedback](https://zenable.io/feedback?utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=feedback) or email [support@zenable.io](mailto:support@zenable.io)
  </Accordion>

  <Accordion title="MCP server not appearing">
    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
  </Accordion>

  <Accordion title="My files aren't being reviewed">
    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
    * **File stashed without pop**: If the agent stashes changes and doesn't pop them back, the files aren't in the working tree and won't be reviewed

    These are expected behaviors — the MCP server focuses on what the agent actually changed during the current session.

    <Tip>
      **For complete coverage**: Use [GitHub](https://docs.zenable.io/integrations/vcs-reviewers/github?utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=pr-reviews) or [GitLab](https://docs.zenable.io/integrations/vcs-reviewers/gitlab?utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=mr-reviews) 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.
    </Tip>
  </Accordion>

  <Accordion title="Extra files are being reviewed that I didn't expect">
    If the agent performs a **rebase**, **merge**, or **git pull** during a session, the review may include files from upstream commits that the agent didn't write. This happens because the hook compares your code against a checkpoint taken at prompt submit time, and these operations bring in external commits that widen the diff.

    This is by design — reviewing extra files is safer than missing the agent's actual changes. The extra files automatically drop off on the next review cycle as the checkpoint advances past the merge/rebase point.

    Common triggers:

    * `git rebase main` — base branch files appear in diff
    * `git merge main` or `git pull` — upstream files appear in diff
    * `git cherry-pick` — cherry-picked commit's files appear in diff

    <Tip>
      This is a one-time effect per operation. After the first review, subsequent reviews only include files the agent changed since the last review.
    </Tip>
  </Accordion>
</AccordionGroup>

For more detailed troubleshooting, see our [troubleshooting guide](/integrations/mcp/troubleshooting).

## Next Steps

* Learn about the [MCP Server](/integrations/mcp/server) and the tools it exposes to your assistant
* [Assess existing codebases](/use-cases/legacy-code-assessment)
* [Configure policies](https://www.zenable.app?utm_source=docs\&utm_medium=mcp-getting-started\&utm_content=configure-policies) for your team