Zendesk MCP — VS Code / Cursor Extension

Configure and launch the Zendesk MCP server for Cursor, VS Code, VSCodium, and any Open VSX-compatible IDE. Setup wizard, OS keychain credential storage, 14 AI tools for support ticket management.

mcp · zendesk · cursor · github-copilot · claude · ai-agents · customer-support · vscode-extension

Author: Markus van Kempen
Email: markus.van.kempen@gmail.com · mvk@ca.ibm.com
Website: markusvankempen.github.io
No bug too small, no syntax too weird.

Table of contents

• What the extension does
• Install
• First-time setup
• Commands
• Settings
• How credentials are stored
• What mcp.json looks like
• Config file locations
• Build from source
• Development (Extension Host)
• Publish to marketplaces
• Architecture
• Troubleshooting
• Documentation

What the extension does

The extension is a configuration manager, not a process manager. It:

1. Lets you pick a connection mode (npm npx, local JS, local Python, or Code Engine remote)
2. Provides a sidebar UI (Activity Bar icon) for setup, diagnostics, and quick-start prompts
3. Stores the API token in the OS keychain (SecretStorage) for local modes
4. Writes mcp.json for Cursor, VS Code, Claude Desktop, and workspace folders
5. Registers an MCP provider so Copilot Chat can discover the server

The IDE's native MCP client spawns the server (stdio or SSE) — the extension does not run the process itself.

📖 Full extension guide: docs/ide/EXTENSION.md

Connection modes

Switch modes: Zendesk MCP: Select Connection Mode or Setup Wizard.

Install

From VS Code Marketplace

1. Open VS Code Extensions panel (Ctrl/Cmd+Shift+X)
2. Search for zendesk-mcp
3. Click Install

From Open VSX (Cursor)

1. Open Cursor Extensions panel
2. Search for zendesk-mcp
3. Click Install

Alternatively, download the .vsix from the GitHub Releases page and install via:

code --install-extension zendesk-mcp-vscode-1.0.0.vsix
# or
cursor --install-extension zendesk-mcp-vscode-1.0.0.vsix

First-time setup

Option A — Setup Wizard (recommended)

1. Command Palette → Zendesk MCP: Setup Wizard
2. Choose connection mode (npx / local-js / local-py / remote)
3. Enter credentials (local) or Code Engine URL (remote)
4. Zendesk MCP: Run Diagnostics
5. Restart IDE if tools don't appear

Option B — npx only

1. Command Palette → Zendesk MCP: Configure Credentials
2. Enter subdomain, email, API token
3. Extension syncs mcp.json automatically

Zendesk API token: Admin → Apps and integrations → APIs → Zendesk API → Token access.

Commands

Open the Command Palette (Ctrl/Cmd+Shift+P) and search for Zendesk MCP:

Diagnostics UI

Activity bar: Zendesk MCP icon → Diagnostics sidebar view.

Or Command Palette → Zendesk MCP: Open Diagnostics Panel / Run Diagnostics.

The panel runs step-by-step checks (like Code Engine /test):

Results show pass/fail per step, timing, JSON details, and a 14-tool checklist grid.

Settings

Configure via File → Preferences → Settings or settings.json:

Important: ZENDESK_API_TOKEN is intentionally not in settings. It is stored in the OS keychain via SecretStorage and is never written to settings.json.

How credentials are stored

SecretStorage uses:

• macOS: macOS Keychain (accessed via Security framework)
• Linux: libsecret / GNOME Keyring / KWallet
• Windows: Windows Credential Manager

The API token is never written to settings.json, never logged, and never appears in the MCP config file in plaintext — it is read from SecretStorage and injected into the config at sync time.

When syncMcpConfig runs:

const apiToken = await context.secrets.get("zendeskMcp.apiToken");
// apiToken is read and written to mcp.json env block
// It never persists in the extension's own state after this point

What mcp.json looks like

The extension writes the correct JSON per connection mode and IDE. Full examples: docs/ide/EXTENSION.md.

npx (default)

{
  "mcpServers": {
    "zendesk-mcp": {
      "command": "npx",
      "args": ["-y", "@markusvankempen/zendesk-mcp-server"],
      "env": {
        "ZENDESK_SUBDOMAIN": "mycompany",
        "ZENDESK_EMAIL": "bot@mycompany.com",
        "ZENDESK_API_TOKEN": "from-keychain-at-sync"
      }
    }
  }
}

VS Code uses "servers" + "type": "stdio" with the same command.

remote (Code Engine)

When connectionMode is remote, the extension writes:

• VS Code: { "type": "sse", "url": "https://<CE_ENDPOINT>/sse" } as zendesk-mcp-remote
• Cursor: { "command": "uvx", "args": ["mcp-proxy", "https://<CE_ENDPOINT>/sse"] }

No local credentials. Set URL via Configure Remote Endpoint.

local-js / local-py

• local-js: node …/packages/zendesk-mcp-server/bin/zendesk-mcp-server.js
• local-py: python3 …/packages/zendesk-mcp-server-py/zendesk_mcp_server.py

If zendeskMcp.useBundledServer is true, npx mode uses global zendesk-mcp-server instead.

Manual remote (without extension)

See docs/ide/README-remote.md and mcp-client-cursor-deployed.json.

Legacy manual Cursor remote snippet:

{
  "mcpServers": {
    "zendesk-mcp-remote": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "https://<CE_ENDPOINT>/sse"
      ]
    }
  }
}

Copy from mcp-client-cursor-deployed.json. Do not hardcode the hostname — resolve CE_ENDPOINT after deploy.

Config file locations

The extension writes to the following locations depending on context:

Existing mcpServers entries from other servers are preserved — the extension only adds or updates the zendesk-mcp key.

Build from source

The public zendesk-mcp repo ships this README only. Extension source is in the private dev monorepo (zendesk-mcp-dev).

# From private dev monorepo root
npm install
npm run build:extension
# Or: cd deployments/vscode-extension && npm install && npm run build

Compiled output: deployments/vscode-extension/dist/extension.js.

Development (Extension Host)

To develop and test the extension locally:

cd deployments/vscode-extension
npm install

1. Open the deployments/vscode-extension/ folder in VS Code
2. Press F5 to launch the Extension Development Host
3. A new VS Code window opens with the extension loaded
4. Run Zendesk MCP: Configure Credentials in the new window to test
5. Set breakpoints in src/extension.ts to debug

Alternatively, open the monorepo root in VS Code — the .vscode/launch.json should include an Extension Host configuration.

Watch mode (auto-rebuild on save)

cd deployments/vscode-extension
npx tsc --watch

Publish to marketplaces

Prerequisites

1. VS Code Marketplace publisher: marketplace.visualstudio.com/manage

   • Create a publisher named markusvankempen
   • Get a Personal Access Token (Azure DevOps → User Settings → Personal Access Tokens)
   • Scope: Marketplace (Manage)

2. Open VSX account: open-vsx.org

   • Create account
   • Generate access token

Manual publish

cd deployments/vscode-extension
npm install

# Package into .vsix
npm run package
# Creates: zendesk-mcp-vscode-1.0.0.vsix

# Publish to VS Marketplace
VSCE_PAT=your_azure_devops_pat npm run publish:vsce

# Publish to Open VSX (Cursor)
OVSX_PAT=your_ovsx_token npm run publish:ovsx

Automated publish (GitHub Actions)

The .github/workflows/publish.yml workflow runs automatically on git tag v*:

# Bump version in deployments/vscode-extension/package.json first
git add deployments/vscode-extension/package.json
git commit -m "chore: bump extension version to 1.0.1"
git tag v1.0.1
git push origin v1.0.1

GitHub Actions will build and publish to npm, VS Marketplace, and Open VSX in sequence. Set these repository secrets:

• NPM_TOKEN
• VSCE_PAT
• OVSX_PAT

Architecture

flowchart TD
    subgraph ext [Extension (runs on IDE startup)]
        CMD1["zendeskMcp.configure\n(interactive wizard)"]
        CMD2["zendeskMcp.syncMcpConfig\n(writes mcp.json)"]
        CMD3["zendeskMcp.showStatus\n(read-only panel)"]

        SS["context.secrets\n(SecretStorage / OS keychain)\n→ ZENDESK_API_TOKEN only"]
        CFG["vscode.workspace.getConfiguration\n(settings.json)\n→ subdomain, email"]
    end

    subgraph files [Config files written by extension]
        F1["~/.cursor/mcp.json"]
        F2["workspace/.cursor/mcp.json"]
        F3["Claude Desktop config"]
    end

    subgraph ide [IDE MCP client (not the extension)]
        NPX["npx @markusvankempen/zendesk-mcp-server\nspawned as child process\nstdin/stdout JSON-RPC"]
    end

    CMD1 --> SS
    CMD1 --> CFG
    CMD2 --> SS
    CMD2 --> CFG
    CMD2 --> files
    files --> NPX
    NPX --> ZD[Zendesk API]

Key design decision: The extension writes config files but does not spawn or manage the MCP server process. The IDE's native MCP client is responsible for spawning, monitoring, and restarting the server. This means:

• The extension does not need to stay active after startup
• No port management or process lifecycle complexity in the extension code
• The server benefits from the IDE's built-in retry and error recovery

Troubleshooting

"No MCP server found" after install

1. Run Zendesk MCP: Configure Credentials if you haven't yet
2. Run Zendesk MCP: Sync MCP Configuration
3. Restart the IDE — the IDE's MCP client reads mcp.json at startup

API token not stored / lost after update

SecretStorage is scoped to extension version in some IDE builds. After extension update, run Zendesk MCP: Configure Credentials again to re-enter and re-store the token.

mcp.json is not being written

1. Run Zendesk MCP: Show Connection Status to see what the extension thinks is configured
2. Check that ZENDESK_SUBDOMAIN and ZENDESK_EMAIL are set in Settings
3. Check that the API token is stored (Status panel shows "API token: stored")
4. Run Zendesk MCP: Sync MCP Configuration manually

Extension is installed but commands don't appear

The extension activates onStartupFinished. If commands are missing, check the Extensions panel to confirm the extension is enabled (not just installed).

Tool calls return 401 from the MCP server

The credentials in mcp.json are incorrect. Run Zendesk MCP: Configure Credentials to update them. Test the token with:

curl -s -u "${ZENDESK_EMAIL}/token:${ZENDESK_API_TOKEN}" \
  "https://${ZENDESK_SUBDOMAIN}.zendesk.com/api/v2/tickets/recent.json"

Cursor: remote Code Engine SSE times out (30s)

Symptom:

MCP IPC timeout: mcp.runCommand.mcp.createClient exceeded 30000ms

when using "url": "https://…codeengine…/sse" for zendesk-mcp-remote.

Fix: Use local stdio instead — this extension writes that config by default:

1. Run Zendesk MCP: Configure Credentials
2. Run Zendesk MCP: Sync MCP Configuration
3. Restart Cursor

That produces a "command": "node" / npx entry with ZENDESK_* env vars (~1s connect). The Code Engine gateway remains available for VS Code SSE, Bob, test UI, and admin panel.

Details: Code Engine troubleshooting — Cursor MCP timeout.

Cursor: mcp.json invalid JSON

If MCP servers stop loading after hand-editing config:

python3 -m json.tool ~/.cursor/mcp.json

Do not nest "mcpServers" inside "mcpServers". Run Zendesk MCP: Sync MCP Configuration to repair the zendesk-mcp entry without touching other servers.

Contributing

Contributions welcome! See CONTRIBUTING.md · CODE_OF_CONDUCT.md

License

MIT License · opensource.org/licenses/MIT

Documentation

Topics & keywords

zendesk · zendesk-mcp · zendesk-api · zendesk-support · mcp · mcp-server · model-context-protocol · vscode-extension · cursor · open-vsx · claude · claude-desktop · github-copilot · copilot · ai-agent · ai-agents · tool-calling · llm-tools · customer-support · customer-service · helpdesk · help-desk · service-desk · support-tickets · ticketing · crm · watsonx · watsonx-orchestrate · ibm-cloud · ibm-code-engine · typescript · npx · automation

Author: Markus van Kempen
Email: markus.van.kempen@gmail.com · mvk@ca.ibm.com
Website: markusvankempen.github.io
No bug too small, no syntax too weird.