@siddharth.sharma/jenkins-mcp

Jenkins MCP server for CI/CD operations. This package runs as a stdio MCP server.

Cursor mcp.json setup

{
  "mcpServers": {
    "jenkins-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@siddharth.sharma/jenkins-mcp",
        "stdio"
      ],
      "env": {
        "JENKINS_SECRET_JSON_FILE": "/Users/<you>/.mcp-secrets/jenkins-secret.json"
      }
    }
  }
}

Secrets and environment

Preferred option:

• JENKINS_SECRET_JSON_FILE (recommended)
• JENKINS_SECRET_JSON (inline JSON)

Secret JSON shape:

{
  "instances": [
    {
      "id": "rvm",
      "baseUrl": "https://rvm.example.com/",
      "user": "ci-bot",
      "apiKey": "replace-me"
    },
    {
      "id": "app-deployer",
      "baseUrl": "https://deploy.example.com/",
      "user": "ci-bot",
      "apiKey": "replace-me"
    }
  ]
}

Alternative configuration:

• JENKINS_INSTANCES as a JSON string with the same instances shape.
• Named variables:
  • RVM_JENKINS_BASE_URL, RVM_JENKINS_API_KEY, and JENKINS_USER (or RVM_JENKINS_USER)
  • APP_DEPLOYER_JENKINS_BASE_URL, APP_DEPLOYER_JENKINS_API_KEY, and JENKINS_USER (or APP_DEPLOYER_JENKINS_USER)

Optional:

• JENKINS_TIMEOUT_MS (default 15000)
• JENKINS_VERIFY_TLS (true or false, default true)

Available tools

• jenkins_list_instances, jenkins_list_allowed_jobs
• jenkins_trigger_job, jenkins_abort_job
• jenkins_get_job_status, jenkins_get_last_build
• jenkins_get_job_parameter_definitions, jenkins_get_build_parameters
• jenkins_queue_to_build, jenkins_list_running_jobs, jenkins_console_tail
• help: quick usage and safety guide.
• echo: connectivity check.

Recommended usage flow

1. Call help.
2. Call jenkins_list_instances.
3. Call jenkins_list_allowed_jobs.
4. Inspect parameters before triggering jobs.
5. Use jenkins_trigger_job and jenkins_abort_job only with explicit approval and confirmed: true.