Add the Jenkins MCP server to Cursor

Config last verified Jun 1, 2026

The exact config to run Jenkins in Cursor — paste it in, restart, and the tools load.

Prerequisites

Cursor installed.
MCP_JENKINS_URL — URL of your Jenkins controller. Comma-separated for multiple instances.
MCP_JENKINS_USER — Jenkins username used to authenticate. Comma-separated to match multiple instances.
MCP_JENKINS_API_TOKEN — Jenkins API token for the user, generated under your Jenkins account's security settings.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.json

json

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": [
        "--yes",
        "@kud/mcp-jenkins@latest"
      ],
      "env": {
        "MCP_JENKINS_URL": "<MCP_JENKINS_URL>",
        "MCP_JENKINS_USER": "<MCP_JENKINS_USER>",
        "MCP_JENKINS_API_TOKEN": "<MCP_JENKINS_API_TOKEN>"
      }
    }
  }
}

3. Restart Cursor and confirm the Jenkins tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Jenkins MCP server