Jenkins MCP Server

TypeScript MCP server that connects AI agents to Jenkins. Supports stdio and Streamable HTTP transports, plus a local web UI to test credential authentication/authorization and copy agent configuration snippets.

Developed by oshaani.com · © oshaani.com. All rights reserved.

Features

• MCP tools for jobs, builds, logs, queue, nodes, identity, and auth checks

• stdio mode for Cursor, Claude Desktop, VS Code

• HTTP mode with Streamable MCP endpoint at /mcp

• Web UI to test Jenkins username/API token auth and permission probes

• Ready-made config snippets for AI agents

• Unit tests with Vitest

Related MCP server: Jenkins MCP Server

Quick start

npm install
npm run build
cp .env.example .env   # then edit credentials

Local Jenkins in Docker (recommended for testing)

docker compose up -d
# Wait until healthy, then copy the generated API token into .env:
docker exec jenkins-mcp-test cat /var/jenkins_home/mcp-api-token.txt

Default test login:

Put the token from mcp-api-token.txt into .env as JENKINS_API_TOKEN, then:

npm run start:http

Open http://127.0.0.1:3100 and run Test authentication.

Stop Jenkins later with docker compose down (add -v to wipe data).

HTTP + UI

npm run start:http

Open http://127.0.0.1:3100 to:

1. Test authentication and authorization against your Jenkins

2. Copy MCP config for Cursor / Claude Desktop / VS Code

Stdio (AI agents)

npm run start:stdio

Environment

Cursor MCP config (stdio)

{
  "mcpServers": {
    "jenkins": {
      "command": "node",
      "args": ["/absolute/path/to/Jenkins MCP/dist/index.js", "stdio"],
      "env": {
        "JENKINS_URL": "https://jenkins.example.com",
        "JENKINS_USERNAME": "your-user",
        "JENKINS_API_TOKEN": "your-api-token"
      }
    }
  }
}

Cursor MCP config (HTTP + headers)

Pass Jenkins credentials from the agent on every request:

{
  "mcpServers": {
    "jenkins": {
      "url": "http://127.0.0.1:3100/mcp",
      "headers": {
        "X-Jenkins-Url": "http://127.0.0.1:8080",
        "X-Jenkins-Username": "admin",
        "X-Jenkins-Api-Token": "your-api-token"
      }
    }
  }
}

Header values override server .env for that MCP session. You can also use Authorization: Basic base64(username:apiToken) plus X-Jenkins-Url.

Cursor MCP config (HTTP + server env)

{
  "mcpServers": {
    "jenkins": {
      "url": "http://127.0.0.1:3100/mcp"
    }
  }
}

MCP tools

Development

npm test
npm run typecheck
npm run dev

License

MIT

Copyright © oshaani.com. Developed by oshaani.com. All rights reserved.