π©Ί Troubleshooting
Common issues and fixes when running the Jenkins MCP server.
π» 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/jsonIf this returns JSON, your credentials are valid!
β±οΈ "Jenkins request timed out"
That message comes from this server, not from Jenkins β every request is bounded by a 10-second deadline, and a large or busy instance can take longer than that to answer a single call. Nothing was refused; the server stopped waiting.
Time the call yourself to see what your instance actually needs:
time curl -u username:token https://your-jenkins.com/job/my-job/api/jsonIf that sits comfortably over 10 seconds, raise the deadline past it:
export MCP_JENKINS_TIMEOUT_MS="30000"See Configuration for the CLI equivalent.
π¨ 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π 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:devOpens http://localhost:5173 - test all tools interactively!