开源MCP工具

Prerequisites

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

Installation

Option 1: Via npm (recommended once published):

```bash

No installation needed! Just use npx in your MCP config

npx --yes @kud/mcp-jenkins@latest

**Option 2: Local installation:**

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.

---

🔨 Build Operations (9 tools)

Build Errors

```bash

Clean rebuild

npm run clean && npm run build ```

🚀 Quick Start

💬 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*

---

Examples

All CLI args:

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

Mixed (CLI overrides env):

```bash MCP_JENKINS_USER=dev_user node dist/index.js --url https://jenkins.com --api-token xyz789

Configuration Priority

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

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

Save config to jenkins-mcp.json

copilot --additional-mcp-config @jenkins-mcp.json

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

#### Option 4: Multiple Jenkins instances

#### Option 5: Allow All Tools (Non-Interactive)

For scripts and automation:

</details>

---

⚙️ Configuration

Uses: URL from CLI, token from CLI, user from env

```

---

Get Your Jenkins API Token

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

Step 1: Access Security Settings

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

Step 2: Create API Token

1. Scroll to the API Token section
2. Under "Current token(s)", click the Add new token button
3. Enter a descriptive name (e.g., "Jenkins MCP" or "AI Assistant")
4. Click Generate
5. ⚠️ 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.

Instances named "pipeline" and "scheduler" automatically from hostnames

```

Verify: claude mcp list should show jenkins

</details>

---

Development Workflow

```bash

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):

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

🐛 Troubleshooting