Jenkins MCP Server

     ██╗███████╗███╗   ██╗██╗  ██╗██╗███╗   ██╗███████╗    ███╗   ███╗ ██████╗██████╗
     ██║██╔════╝████╗  ██║██║ ██╔╝██║████╗  ██║██╔════╝    ████╗ ████║██╔════╝██╔══██╗
     ██║█████╗  ██╔██╗ ██║█████╔╝ ██║██╔██╗ ██║███████╗    ██╔████╔██║██║     ██████╔╝
██   ██║██╔══╝  ██║╚██╗██║██╔═██╗ ██║██║╚██╗██║╚════██║    ██║╚██╔╝██║██║     ██╔═══╝
╚█████╔╝███████╗██║ ╚████║██║  ██╗██║██║ ╚████║███████║    ██║ ╚═╝ ██║╚██████╗██║
 ╚════╝ ╚══════╝╚═╝  ╚═══╝╚═╝  ╚═╝╚═╝╚═╝  ╚═══╝╚══════╝    ╚═╝     ╚═╝ ╚═════╝╚═╝

A Jenkins MCP server with 37 tools for managing jobs, builds, nodes, views, and CI/CD workflows

Features • Quick Start • Installation • Tools • Development

🌟 Features

🔐 Flexible Authentication - Bearer tokens, Basic auth, OAuth support
⚙️ Flexible Configuration - CLI args or MCP_JENKINS_* env vars (priority-based)
🔒 Tool Filtering - Allowlist or blocklist tools via MCP_JENKINS_ALLOW_TOOLS / MCP_JENKINS_BLOCK_TOOLS
🔀 Multi-Instance Support - Connect to multiple Jenkins servers in one MCP entry, select per tool call
🛠️ 37 Tools - Comprehensive Jenkins API coverage
⚡ Modern Stack - TypeScript 5.3+, ES2023, Native Fetch API
📦 MCP Protocol - Native integration with Claude Desktop, Claude Code CLI
🔄 Real-time Monitoring - Build status, queue management, pipeline stages
🧪 Test Results - View test pass/fail counts and suites
🎯 Job Control - Enable/disable, trigger, stop, replay builds
📊 System Info - Nodes, plugins, version info
🔍 Debug Tools - MCP inspector for testing

🚀 Quick Start

Prerequisites

Node.js 20+
Jenkins API token (how to get one)

Installation

Option 1: Via npm (recommended once published):

# No installation needed! Just use npx in your MCP config
npx --yes @kud/mcp-jenkins@latest

Option 2: Local installation:

git clone https://github.com/kud/mcp-jenkins.git
cd mcp-jenkins
npm install
npm run build

Configuration Priority

The server supports 2 ways to provide configuration (highest to lowest priority):

CLI arguments - --url, --user, --api-token, --bearer-token
MCP_JENKINS_* environment variables - MCP_JENKINS_URL, MCP_JENKINS_USER, etc.

Quick Setup Example (Claude CLI)

Using environment variables (recommended):

claude mcp add --transport stdio --scope user jenkins \
  --env MCP_JENKINS_URL=https://your-jenkins.com \
  --env MCP_JENKINS_USER=your_username \
  --env MCP_JENKINS_API_TOKEN=your_token \
  -- npx --yes @kud/mcp-jenkins@latest

Using CLI arguments (override env vars):

claude mcp add --transport stdio --scope user jenkins \
  -- npx --yes @kud/mcp-jenkins@latest \
  --url https://your-jenkins.com \
  --user your_username \
  --api-token your_token

If installed locally:

claude mcp add --transport stdio --scope user jenkins \
  -- node ~/path/to/mcp-jenkins/dist/index.js \
  --url https://your-jenkins.com \
  --user your_username \
  --api-token your_token

✅ Done! Now you can use Jenkins commands in your AI assistant.

📚 Installation Guides

Choose your development environment:

Claude Code CLI - Command line interface
Claude Code Web - Browser-based Claude
Claude Desktop - Desktop application
VSCode - With Cline, Claude Dev, Continue
Cursor - AI-first IDE
Windsurf - AI-powered code editor
GitHub Copilot - In VSCode or standalone
GitHub Copilot CLI - Terminal tool
JetBrains IDEs - IntelliJ, WebStorm, PyCharm, GoLand, etc.

🎯 Claude Code CLI

For: Claude AI via command line interface

Click to expand Claude Code CLI setup

Add the Jenkins MCP server to Claude CLI:

Via npm with env vars (recommended):

claude mcp add --transport stdio --scope user jenkins \
  --env MCP_JENKINS_URL=https://pipeline.yourcompany.com \
  --env MCP_JENKINS_USER=your_username \
  --env MCP_JENKINS_API_TOKEN=your_api_token \
  -- npx --yes @kud/mcp-jenkins@latest

Via npm with CLI args:

claude mcp add --transport stdio --scope user jenkins \
  -- npx --yes @kud/mcp-jenkins@latest \
  --url https://pipeline.yourcompany.com \
  --user your_username \
  --api-token your_api_token

Local installation with CLI args:

claude mcp add --transport stdio --scope user jenkins \
  -- node $HOME/path/to/mcp-jenkins/dist/index.js \
  --url https://pipeline.yourcompany.com \
  --user your_username \
  --api-token your_api_token

Multiple Jenkins instances:

claude mcp add --transport stdio --scope user jenkins \
  --env MCP_JENKINS_URL="https://pipeline.yourcompany.com,https://scheduler.yourcompany.com" \
  --env MCP_JENKINS_USER="your_username,your_username" \
  --env MCP_JENKINS_API_TOKEN="token1,token2" \
  -- npx --yes @kud/mcp-jenkins@latest
# Instances named "pipeline" and "scheduler" automatically from hostnames

Verify: claude mcp list should show jenkins

🌐 Claude Code Web

For: Claude.ai in your browser

Click to expand Claude Web setup

⚠️ Not supported. Claude.ai web interface doesn't support custom MCP servers yet.

Alternatives:

Use desktop clients (see below)
Use CLI tools (see above)
Test via MCP Inspector: npm run inspect:dev → http://localhost:5173

🖥️ Claude Desktop

For: Claude AI desktop application

Click to expand Claude Desktop setup

1. Open Configuration File

macOS:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Windows:

notepad %APPDATA%\Claude\claude_desktop_config.json

2. Add Configuration

Via npm with env vars (recommended):

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com",
        "MCP_JENKINS_USER": "your_username",
        "MCP_JENKINS_API_TOKEN": "your_api_token"
      }
    }
  }
}

Via npm with CLI args:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": [
        "--yes",
        "@kud/mcp-jenkins@latest",
        "--url",
        "https://pipeline.yourcompany.com",
        "--user",
        "your_username",
        "--api-token",
        "your_api_token"
      ]
    }
  }
}

Local installation with CLI args:

{
  "mcpServers": {
    "jenkins": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-jenkins/dist/index.js",
        "--url",
        "https://pipeline.yourcompany.com",
        "--user",
        "your_username",
        "--api-token",
        "your_api_token"
      ]
    }
  }
}

Bearer token example:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": [
        "--yes",
        "@kud/mcp-jenkins@latest",
        "--url",
        "https://pipeline.yourcompany.com",
        "--bearer-token",
        "your_bearer_token"
      ]
    }
  }
}

Multiple Jenkins instances:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com,https://scheduler.yourcompany.com",
        "MCP_JENKINS_USER": "your_username,your_username",
        "MCP_JENKINS_API_TOKEN": "token1,token2"
      }
    }
  }
}

3. Restart

Quit (Cmd+Q / Alt+F4) and reopen Claude Desktop

📝 VSCode

For: VSCode with MCP-compatible extensions (Cline, Claude Dev, Continue)

Click to expand VSCode setup

Cline:

Settings (Cmd+, / Ctrl+,) → Search "Cline: MCP Settings" → Edit in settings.json:

{
  "cline.mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["@kud/mcp-jenkins"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com",
        "MCP_JENKINS_USER": "your_username",
        "MCP_JENKINS_API_TOKEN": "your_api_token"
      }
    }
  }
}

Multiple Jenkins instances:

{
  "cline.mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["@kud/mcp-jenkins"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com,https://scheduler.yourcompany.com",
        "MCP_JENKINS_USER": "your_username,your_username",
        "MCP_JENKINS_API_TOKEN": "token1,token2"
      }
    }
  }
}

Or for local installation, use "command": "node" and "args": ["/absolute/path/to/mcp-jenkins/dist/index.js"]

Claude Dev / Continue:

Command Palette (Cmd+Shift+P) → "MCP: Edit Config" → Add similar configuration

Reload window after configuration

🌐 Cursor

For: Cursor IDE with built-in AI

Click to expand Cursor setup

Settings (Cmd+, / Ctrl+,) → Search "MCP" → Edit Config or open ~/.cursor/mcp_config.json:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com",
        "MCP_JENKINS_USER": "your_username",
        "MCP_JENKINS_API_TOKEN": "your_api_token"
      }
    }
  }
}

Multiple Jenkins instances:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com,https://scheduler.yourcompany.com",
        "MCP_JENKINS_USER": "your_username,your_username",
        "MCP_JENKINS_API_TOKEN": "token1,token2"
      }
    }
  }
}

Or for local installation, use "command": "node" and "args": ["/absolute/path/to/mcp-jenkins/dist/index.js"]

Restart Cursor (Cmd+Q / Alt+F4) after configuration

🌊 Windsurf

For: Windsurf AI-powered code editor

Click to expand Windsurf setup

Settings → AI Settings → Model Context Protocol → Add Server:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com",
        "MCP_JENKINS_USER": "your_username",
        "MCP_JENKINS_API_TOKEN": "your_api_token"
      }
    }
  }
}

Multiple Jenkins instances:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com,https://scheduler.yourcompany.com",
        "MCP_JENKINS_USER": "your_username,your_username",
        "MCP_JENKINS_API_TOKEN": "token1,token2"
      }
    }
  }
}

Or edit ~/.windsurf/mcp_settings.json directly. For local installation, use "command": "node" with full path.

Restart Windsurf after configuration.

🤖 GitHub Copilot

For: GitHub Copilot in VSCode or other editors

Click to expand GitHub Copilot setup

⚠️ Not supported. GitHub Copilot doesn't support MCP servers.

Options:

In VSCode: Install Copilot + Cline/Claude Dev. Use Copilot for coding, Cline/Claude Dev for Jenkins (see VSCode section)
In terminal: Use Copilot for coding suggestions, an MCP-compatible CLI for Jenkins (see CLI sections above)
No MCP: Use code in src/lib/jenkins-client.ts as examples for direct API calls

💻 GitHub Copilot CLI

For: New GitHub Copilot CLI (@github/copilot) in your terminal

Click to expand GitHub Copilot CLI setup

Note: This is for the NEW Copilot CLI (npm install -g @github/copilot), not the old gh copilot extension.

Option 1: Config File with Env Vars (Recommended)

Create or edit ~/.copilot/mcp-config.json:

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com",
        "MCP_JENKINS_USER": "your_username",
        "MCP_JENKINS_API_TOKEN": "your_api_token"
      }
    }
  }
}

Then run: copilot

Option 2: Config File with CLI Args

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": [
        "--yes",
        "@kud/mcp-jenkins@latest",
        "--url",
        "https://pipeline.yourcompany.com",
        "--user",
        "your_username",
        "--api-token",
        "your_api_token"
      ]
    }
  }
}

Option 3: Inline Config with CLI Args

Pass MCP config directly via command line:

copilot --additional-mcp-config '{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": [
        "--yes", "@kud/mcp-jenkins@latest",
        "--url", "https://pipeline.yourcompany.com",
        "--user", "your_username",
        "--api-token", "your_api_token"
      ]
    }
  }
}'

Or save to a file and reference it:

# Save config to jenkins-mcp.json
copilot --additional-mcp-config @jenkins-mcp.json

For local installation, use "command": "node" with path in args:

"args": ["/absolute/path/to/mcp-jenkins/dist/index.js", "--url", "...", "--user", "...", "--api-token", "..."]

Option 4: Multiple Jenkins instances

{
  "mcpServers": {
    "jenkins": {
      "command": "npx",
      "args": ["--yes", "@kud/mcp-jenkins@latest"],
      "env": {
        "MCP_JENKINS_URL": "https://pipeline.yourcompany.com,https://scheduler.yourcompany.com",
        "MCP_JENKINS_USER": "your_username,your_username",
        "MCP_JENKINS_API_TOKEN": "token1,token2"
      }
    }
  }
}

Option 5: Allow All Tools (Non-Interactive)

For scripts and automation:

copilot --allow-all-tools -p "Check status of mobile-pipeline build"

🔧 All JetBrains IDEs

For: IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, PhpStorm, Rider, CLion, DataGrip

Click to expand JetBrains IDEs setup

Settings (Cmd+, / Ctrl+,) → Tools → AI Assistant → Model Context Protocol → Add Server:

Name: Jenkins
Command: npx
Arguments: --yes @kud/mcp-jenkins@latest

Environment Variables:

MCP_JENKINS_URL=https://pipeline.yourcompany.com
MCP_JENKINS_USER=your_username
MCP_JENKINS_API_TOKEN=your_api_token

Multiple Jenkins instances: set these environment variables:

MCP_JENKINS_URL=https://pipeline.yourcompany.com,https://scheduler.yourcompany.com
MCP_JENKINS_USER=your_username,your_username
MCP_JENKINS_API_TOKEN=token1,token2

For local installation, use Command: node and Arguments: /absolute/path/to/mcp-jenkins/dist/index.js

Apply and restart the IDE.

Alternative: If MCP not available, use MCP-compatible CLI from built-in terminal (Alt+F12 / ⌥F12)

Notes:

Ultimate/Professional editions: Full AI Assistant MCP support
Community editions: Use MCP-compatible CLI from terminal instead

🛠️ Available Tools

📋 Job Operations (11 tools)

Tool	Description
`jenkins_list_jobs`	List all Jenkins jobs
`jenkins_search_jobs`	Search jobs by name
`jenkins_get_job_status`	Get last build status
`jenkins_enable_job`	Enable a disabled job
`jenkins_disable_job`	Disable a job
`jenkins_delete_job`	Delete a job (⚠️ permanent)
`jenkins_get_job_config`	Get job XML configuration
`jenkins_create_job`	Create a new job from XML config
`jenkins_update_job_config`	Update an existing job's XML config
`jenkins_rename_job`	Rename a job
`jenkins_copy_job`	Copy/duplicate a job

🔨 Build Operations (9 tools)

Tool	Description
`jenkins_get_build_status`	Get specific build status
`jenkins_get_recent_builds`	Get recent builds (last N)
`jenkins_trigger_build`	Trigger a new build
`jenkins_stop_build`	Stop/abort running build
`jenkins_delete_build`	Delete a build
`jenkins_replay_build`	Replay a pipeline build
`jenkins_get_console_log`	Get build console output
`jenkins_get_build_changes`	Get Git commits for build
`jenkins_get_pipeline_stages`	Get pipeline stage status

🧪 Testing & Artifacts (3 tools)

Tool	Description
`jenkins_get_test_results`	Get test pass/fail counts
`jenkins_list_artifacts`	List build artifacts
`jenkins_get_artifact`	Download artifact (base64)

📊 Queue Management (2 tools)

Tool	Description
`jenkins_get_queue`	View pending builds
`jenkins_cancel_queue`	Cancel queued build

🖥️ System & Nodes (8 tools)

Tool	Description
`jenkins_list_nodes`	List all agents/nodes
`jenkins_get_node`	Get detailed info on a specific node
`jenkins_toggle_node_offline`	Toggle a node online/offline
`jenkins_get_system_info`	Get Jenkins system info
`jenkins_get_version`	Get Jenkins version
`jenkins_get_plugins`	List installed plugins
`jenkins_quiet_down`	Enable quiet mode (⚠️ requires confirm)
`jenkins_cancel_quiet_down`	Cancel quiet mode

🗂️ Views (2 tools)

Tool	Description
`jenkins_list_views`	List all views with their jobs
`jenkins_get_view`	Get details for a specific view

🔀 Instances & Admin (2 tools)

Tool	Description
`jenkins_list_instances`	List all configured instances with their URLs
`jenkins_safe_restart`	Safely restart Jenkins (⚠️ requires confirm)

Total: 37 Tools covering ~95% of Jenkins API operations!

💬 Example Conversations

Once configured, interact with Jenkins naturally:

You: "List all my Jenkins jobs"
AI: *Shows list of all jobs*

You: "What's the status of the 'api-backend' build?"
AI: *Shows latest build status, duration, result*

You: "Get the test results for build #42 of 'mobile-pipeline'"
AI: *Shows pass/fail counts, test suites*

You: "Show me the pipeline stages for that failed build"
AI: *Shows which stage failed and durations*

You: "Trigger a build for 'deploy-staging' with VERSION=2.1.0"
AI: *Triggers build with parameters*

You: "Stop build #966 of 'mobile-pipeline'"
AI: *Stops the running build*

You: "Show me the queue"
AI: *Lists all pending builds*

You: "What version of Jenkins are we running?"
AI: *Shows Jenkins version*

🧪 Development

Project Structure

mcp-jenkins/
├── src/
│   ├── common/              # Shared utilities
│   │   ├── env.ts           # Environment config
│   │   ├── errors.ts        # Error handling
│   │   ├── http.ts          # HTTP client (native fetch)
│   │   ├── logger.ts        # JSON logging
│   │   └── index.ts         # Exports
│   ├── lib/
│   │   └── jenkins-client.ts  # Jenkins API client
│   ├── tools/               # 25 MCP tool implementations
│   │   ├── get-job-status.ts
│   │   ├── trigger-build.ts
│   │   ├── get-test-results.ts
│   │   ├── stop-build.ts
│   │   └── ... (21 more)
│   └── index.ts             # MCP server entrypoint
├── dist/                    # Compiled output
├── package.json
├── tsconfig.json
└── README.md

Available Scripts

Script	Description
`npm run build`	Compile TypeScript to JavaScript
`npm run build:watch`	Watch mode - rebuild on changes
`npm run dev`	Run in development (tsx)
`npm start`	Run compiled server
`npm run inspect`	Open MCP inspector
`npm run inspect:dev`	Inspector in dev mode (no build)
`npm run typecheck`	Type check without building
`npm run clean`	Remove build artifacts

Development Workflow

# Terminal 1: Watch mode
npm run build:watch

# Terminal 2: Test with inspector
npm run inspect:dev

Testing with MCP Inspector

export MCP_JENKINS_URL=https://pipeline.yourcompany.com
export MCP_JENKINS_USER=your_username
export MCP_JENKINS_API_TOKEN=your_token

npm run inspect:dev

Opens http://localhost:5173 - test all tools interactively!

Adding New Tools

Create tool file in src/tools/:

// src/tools/my-new-tool.ts
import { JenkinsClient } from "../lib/jenkins-client.js"

export interface MyToolInput {
  someParam: string
}

export const myNewTool = async (client: JenkinsClient, input: MyToolInput) => {
  // Implementation
  return { result: "success" }
}

Add method to JenkinsClient (src/lib/jenkins-client.ts)
Register in src/index.ts:
- Import the tool
- Add to tools array
- Add to toolHandlers map
Rebuild:

npm run build

⚙️ Configuration

Priority System

The server uses a 2-tier priority system for configuration:

CLI Arguments (Highest Priority)
- --url <url> - Jenkins server URL
- --user <username> - Username for Basic auth
- --api-token <token> - API token for Basic auth
- --bearer-token <token> - Bearer token for OAuth/token auth
MCP_JENKINS_* Environment Variables
- MCP_JENKINS_URL
- MCP_JENKINS_USER
- MCP_JENKINS_API_TOKEN
- MCP_JENKINS_BEARER_TOKEN

Multiple Instances

Connect to more than one Jenkins server in a single MCP entry using comma or pipe-separated values.

Automatic naming (derived from URL hostname):

export MCP_JENKINS_URL="https://pipeline.yourcompany.com,https://scheduler.yourcompany.com"
export MCP_JENKINS_USER="your_username,your_username"
export MCP_JENKINS_API_TOKEN="token1,token2"
# Instances are automatically named "pipeline" and "scheduler"

Custom naming with MCP_JENKINS_INSTANCES:

Use MCP_JENKINS_INSTANCES when you want explicit names (e.g., the hostname isn't descriptive enough, or both instances share the same host):

export MCP_JENKINS_INSTANCES="ci,prod"
export MCP_JENKINS_URL="https://jenkins.yourcompany.com/ci,https://jenkins.yourcompany.com/prod"
export MCP_JENKINS_USER="your_username,your_username"
export MCP_JENKINS_API_TOKEN="token1,token2"
# Instances are named "ci" and "prod"

The number of values in MCP_JENKINS_INSTANCES must match the number of URLs.

Then pass instance in tool calls:

"Trigger a build for 'deploy' on the scheduler instance"
"List jobs on ci"

The first instance is always the default — tools work without instance if you only have one server.

Note: Use | as delimiter instead of , if any value might contain a comma (e.g., unusual URLs).

Tool Filtering

Control which tools are exposed to the AI using an allowlist or blocklist.

Allowlist — expose only specific tools:

export MCP_JENKINS_ALLOW_TOOLS="jenkins_list_jobs,jenkins_get_job_status,jenkins_get_build_status"

Blocklist — hide specific tools (all others remain available):

export MCP_JENKINS_BLOCK_TOOLS="jenkins_delete_job,jenkins_trigger_build,jenkins_safe_restart"

If both are set, MCP_JENKINS_ALLOW_TOOLS takes precedence.

Read-only monitoring preset — block all write/destructive tools:

export MCP_JENKINS_BLOCK_TOOLS="jenkins_trigger_build,jenkins_stop_build,jenkins_delete_build,jenkins_cancel_queue,jenkins_enable_job,jenkins_disable_job,jenkins_delete_job,jenkins_create_job,jenkins_update_job_config,jenkins_rename_job,jenkins_copy_job,jenkins_toggle_node_offline,jenkins_quiet_down,jenkins_cancel_quiet_down,jenkins_safe_restart,jenkins_replay_build"

Examples

All CLI args:

node dist/index.js --url https://jenkins.com --user admin --api-token abc123

Mixed (CLI overrides env):

MCP_JENKINS_USER=dev_user node dist/index.js --url https://jenkins.com --api-token xyz789
# Uses: URL from CLI, token from CLI, user from env

🔐 Authentication

Get Your Jenkins API Token

Follow these steps to create an API token for the MCP server:

Step 1: Access Security Settings

Log in to your Jenkins instance
Click your username in the top-right corner
Select Configure from the dropdown menu
In the left sidebar, click Security

Step 2: Create API Token

Scroll to the API Token section
Under "Current token(s)", click the Add new token button
Enter a descriptive name (e.g., "Jenkins MCP" or "AI Assistant")
Click Generate
⚠️ IMPORTANT: Copy the token immediately - it will only be shown once!

Step 3: Save the Token

Store the token securely - you'll need it for configuration:

For Bearer Token auth: Use it as MCP_JENKINS_BEARER_TOKEN
For Basic auth: Use it as MCP_JENKINS_API_TOKEN (along with MCP_JENKINS_USER)

Example token format: 11abcd1234567890abcdef1234567890ab

💡 Tip: You can see all your active tokens in the "Current token(s)" list. Each shows when it was created and last used, helping you manage and rotate tokens regularly.

Bearer Token vs Basic Auth

Bearer Token (Recommended):

--env MCP_JENKINS_BEARER_TOKEN=your_token

Basic Auth:

--env MCP_JENKINS_USER=your_username
--env MCP_JENKINS_API_TOKEN=your_token

OAuth Support

This server forwards any Authorization header to Jenkins. If your Jenkins uses OAuth (via plugins), just pass the OAuth token as MCP_JENKINS_BEARER_TOKEN.

🐛 Troubleshooting

Server Not Showing in Claude

✅ Check path is absolute
✅ Run npm install && npm run build
✅ Verify environment variables
✅ Restart Claude completely

Authentication Errors

# Test your credentials
curl -u username:token https://your-jenkins.com/api/json

If this returns JSON, your credentials are valid!

Build Errors

# Clean rebuild
npm run clean && npm run build

Check Logs

Claude Desktop logs:

macOS: ~/Library/Logs/Claude/mcp*.log
Windows: %APPDATA%\Claude\logs\mcp*.log

Claude Code CLI logs:

claude mcp get jenkins

🔒 Security Best Practices

✅ Use environment variables (never hardcode tokens)
✅ Use bearer tokens over basic auth when possible
✅ Rotate tokens regularly
✅ Use restricted tokens (limit permissions in Jenkins)
✅ Never commit tokens to version control
✅ Protect config files (claude_desktop_config.json)

📊 Tech Stack

Runtime: Node.js 20+
Language: TypeScript 5.3+
Target: ES2023
Protocol: MCP 1.0 (stdio transport)
HTTP Client: Native Fetch API
Module System: ESM

🤝 Contributing

Contributions welcome! Please ensure:

TypeScript strict mode compliance
All tools properly typed
Build passes: npm run build
Tools registered in both tools array and toolHandlers

📄 License

MIT License - see LICENSE file

🙏 Acknowledgments

Built with Model Context Protocol
Jenkins REST API by Jenkins Project

📮 Support

🐛 Issues: GitHub Issues
💬 Discussions: GitHub Discussions

Made with ❤️ for the DevOps & AI community

⭐ Star this repo if it helped you!

Back to Top

Name		Name	Last commit message	Last commit date
Latest commit History 62 Commits
.github/workflows		.github/workflows
docs		docs
src		src
test		test
.gitignore		.gitignore
.mcp.json		.mcp.json
CHANGELOG.md		CHANGELOG.md
CLAUDE.md		CLAUDE.md
LICENSE		LICENSE
README.md		README.md
mock.ts		mock.ts
package.json		package.json
server.mcp.json		server.mcp.json
tsconfig.json		tsconfig.json
vitest.config.ts		vitest.config.ts

Folders and files

Latest commit

History

Repository files navigation

Jenkins MCP Server

🌟 Features

🚀 Quick Start

Prerequisites

Installation

Configuration Priority

Quick Setup Example (Claude CLI)

📚 Installation Guides

🎯 Claude Code CLI

🌐 Claude Code Web

🖥️ Claude Desktop

1. Open Configuration File

2. Add Configuration

3. Restart

📝 VSCode

🌐 Cursor

🌊 Windsurf

🤖 GitHub Copilot

💻 GitHub Copilot CLI

Option 1: Config File with Env Vars (Recommended)

Option 2: Config File with CLI Args

Option 3: Inline Config with CLI Args

Option 4: Multiple Jenkins instances

Option 5: Allow All Tools (Non-Interactive)

🔧 All JetBrains IDEs

🛠️ Available Tools

📋 Job Operations (11 tools)

🔨 Build Operations (9 tools)

🧪 Testing & Artifacts (3 tools)

📊 Queue Management (2 tools)

🖥️ System & Nodes (8 tools)

🗂️ Views (2 tools)

🔀 Instances & Admin (2 tools)

💬 Example Conversations

🧪 Development

Project Structure

Available Scripts

Development Workflow

Testing with MCP Inspector

Adding New Tools

⚙️ Configuration

Priority System

Multiple Instances

Tool Filtering

Examples

🔐 Authentication

Get Your Jenkins API Token

Step 1: Access Security Settings

Step 2: Create API Token

Step 3: Save the Token

Bearer Token vs Basic Auth

OAuth Support

🐛 Troubleshooting

Server Not Showing in Claude

Authentication Errors

Build Errors

Check Logs

🔒 Security Best Practices

📊 Tech Stack

🤝 Contributing

📄 License

🙏 Acknowledgments

📮 Support

About

Topics

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Contributors

Uh oh!

Packages