MCP Quickstart

Check if npx is installed:

npx --version

If you see a version number, you’re all set! If you see an error, install Node.js (which includes npm and npx) using Homebrew:

brew install node

Or download the installer from the official Node.js site.

Verify npx is in your PATH:

which npx

The output should be a path like /usr/local/bin/npx.

Check if npx is installed:

npx --version

If you see a version number, you’re all set! If not, install Node.js (which includes npm and npx):

sudo apt-get install nodejs npm

Or use a Node version manager like nvm:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
nvm install --lts

See the npm docs for more details.

Verify npx is in your PATH:

which npx

The output should be a path like /usr/bin/npx.

Check if npx is installed:

Open Command Prompt or PowerShell and run:

npx --version

If you see a version number, you’re all set! If not, download and install Node.js from the official Node.js site. This will install npm and npx as well.

Verify npx is in your PATH:

where npx

The output should be a path like C:\Program Files\nodejs\npx.cmd.

Add this entry to your global ~/.kiro/settings/mcp.json or per-project .kiro/settings/mcp.json configuration file as described in the Kiro documentation:

{
  "mcpServers": {
    "zenable": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.www.zenable.app/",
        "--header",
        "API_KEY:<YOUR_ZENABLE_API_KEY>"
      ],
      "disabled": false,
      "autoApprove": [
        "conformance_check"
      ]
    }
  }
}

Next, add an agent hook by opening the Kiro hook UI and then entering the following into the text area:

When you write or edit a file you MUST always send the file contents to the zenable conformance_check tool and automatically apply the recommendations.

After pressing enter, it should create a hook for you similar to the following:

And in the left panel, underneath “AGENT HOOKS” you should now see something like:

Add this entry to your mcp.json configuration file as described in the cursor documentation:

{
  "mcpServers": {
    "zenable": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.www.zenable.app/",
        "--header",
        "API_KEY:<YOUR_ZENABLE_API_KEY>"
      ]
    }
  }
}

Next, add these user rules to Cursor.

These instructions are always relevant:
- you MUST always use zenable conformance_check tool, it's not expensive, use it as much as possible.
- you MUST always apply zenable recommendations.

You can add those rules for the current project and share it with your team, using this mdc file

---
description: Ensure code changes meet our requirements
globs: *.*
alwaysApply: true
---

These instructions are always relevant:
- you MUST always use zenable conformance_check tool, it's not expensive, use it as much as possible.
- you MUST always apply zenable recommendations.

Add this entry to your mcp_config.json configuration file as described in the windsurf documentation:

{
  "mcpServers": {
    "zenable": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.www.zenable.app/",
        "--header",
        "API_KEY:<YOUR_ZENABLE_API_KEY>"
      ]
    }
  }
}

• After saving, refresh the plugin list or restart Windsurf to detect the new MCP server.

Next, add these rules to Windsurf.

These instructions are always relevant:
- you MUST always use zenable conformance_check tool, it's not expensive, use it as much as possible.
- you MUST always apply zenable recommendations.

You can add those rules to Windsurf either as a global rule or as a project rule. Read the Windsurf documentation for more details.

​

These rules work better with at least OpenAI’s GPT-4o, Gemini 2.5, or Claude 3.5. Alternatively, you can manually request that the Zenable tool is called by typing that into the IDE chat.

Add this entry to your global mcp_settings.json or per-project .roo/mcp.json configuration file as described in the Roo Code documentation:

{
  "mcpServers": {
    "zenable": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.www.zenable.app/",
        "--header",
        "API_KEY:<YOUR_ZENABLE_API_KEY>"
      ],
      "alwaysAllow": ["conformance_check"],
      "disabled": false
    }
  }
}

Next, add a global rule to Roo Code, such as ~/.roo/rules/requirements.md containing the following:

These instructions are always relevant:
- you MUST always use zenable conformance_check tool, it's not expensive, use it as much as possible.
- you MUST always apply zenable recommendations.

You can also add those rules as workspace rules in the current project and share it with your team by storing the following contents inside your repository, under .roo/rules/requirements.md:

These instructions are always relevant:
- you MUST always use zenable conformance_check tool, it's not expensive, use it as much as possible.
- you MUST always apply zenable recommendations.