MCP Quickstart - Zenable MCP Server Docs

End-user installation

First you’ll need an API Key from us to use the MCP server.

Visit our get started page, fill out the sign up form, and you’ll receive your key.

Next, you’ll update your editor / IDE / LLM client to connect to the Zenable MCP server’s endpoint.

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

{
    "mcpServers": {
        "zenable": {
            "url": "https://mcp.www.zenable.app/",
            "headers": {
                "API_KEY": "${input:zenable_api_key}"
            }
        }
    },
    "inputs": [
        {
            "type": "promptString",
            "id": "zenable_api_key",
            "description": "Your Zenable API Key",
            "password": true
        }
    ]
}

Next, add these user rules to Cursor.

- After generating code, creating a new file or edit a files you must always check those files with the Zenable tool recommendations from the Zenable MCP server to validate it against the company policies.
- Follow all recommendations and required changes as reported by the Zenable MCP server.

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

zenable_rules.mdc
---
description: Run Zenable Compliance with MCP
globs: *.*
alwaysApply: true
---

- After generating code, creating a new file or editing files you must always check those files with the Zenable tool recommendations from the Zenable MCP server to validate it against the company policies.
- Follow all recommendations and required changes as reported by the Zenable MCP server.

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

{
    "mcpServers": {
        "zenable": {
            "url": "https://mcp.www.zenable.app/",
            "headers": {
                "API_KEY": "${input:zenable_api_key}"
            }
        }
    },
    "inputs": [
        {
            "type": "promptString",
            "id": "zenable_api_key",
            "description": "Your Zenable API Key",
            "password": true
        }
    ]
}

Next, add these user rules to Cursor.

- After generating code, creating a new file or edit a files you must always check those files with the Zenable tool recommendations from the Zenable MCP server to validate it against the company policies.
- Follow all recommendations and required changes as reported by the Zenable MCP server.

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

zenable_rules.mdc
---
description: Run Zenable Compliance with MCP
globs: *.*
alwaysApply: true
---

- After generating code, creating a new file or editing files you must always check those files with the Zenable tool recommendations from the Zenable MCP server to validate it against the company policies.
- Follow all recommendations and required changes as reported by the Zenable MCP server.

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.

- After generating code, creating a new file or edit a files you must always check those files with the Zenable tool recommendations from the Zenable MCP server to validate it against the company policies.
- Follow all recommendations and required changes as reported by the Zenable MCP server.

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

Ensure `npx` is installed and available

Windsurf uses npx to run the Zenable MCP integration. If you don’t already have npx installed, follow the instructions below for your platform:

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

For more information, see the npm documentation.

For more details on the MCP protocol or advanced configuration, see the official documentation for your client (Cursor or Windsurf).

Get Started

​End-user installation

​Ensure npx is installed and available

End-user installation

Ensure `npx` is installed and available