MCP Servers
avisangle/jenkins-mcp-server
An MCP server for interacting with a Jenkins server. Allows you to trigger jobs, check build statuses, and manage your Jenkins instance through MCP.
Our verdict
We have not reviewed avisangle/jenkins-mcp-server yet
No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.
From the listing
About avisangle/jenkins-mcp-server
An MCP server that connects AI agents to a Jenkins instance. It enables triggering jobs, checking build statuses, and managing Jenkins operations through the Model Context Protocol.
Best for
Developers who want to control Jenkins pipelines through an AI agent
Use cases
- Trigger Jenkins jobs from an AI assistant
- Check build status and logs without opening the Jenkins UI
- Automate CI/CD workflows via natural language commands
Notes
2 stars on GitHub. Last updated 2026-02-13.
Pros
- Simple Python implementation easy to extend
- Direct integration with Jenkins for common operations
- Works with any MCP-compatible client
Cons
- Very early stage with only 2 GitHub stars
- Limited to basic job triggering and status checks
- Requires manual setup and Jenkins API credentials
Key facts
What we have checked
- Days since the last commit
- 255
- GitHub forks
- 2
- GitHub stars
- 4
- Releases in the last 90 days
- 0
Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.
How to use
How to set it up
As the listing publishes it. We have not run this install.
Install
pip install -e .Tools exposed
trigger_jobget_job_infolist_jobssearch_jobssearch_and_triggerget_folder_infoget_build_statusget_console_logsummarize_build_logget_pipeline_statuslist_build_artifactsdownload_build_artifactsearch_build_artifacts
Clients the listing names (not checked here)
Claude Desktop
Example client config
{
"mcpServers": {
"jenkins": {
"command": "node",
"args": [
"/path/to/jenkins-mcp-server/bin/jenkins-mcp.js"
],
"env": {
"JENKINS_URL": "http://your-jenkins-server:8080",
"JENKINS_USER": "your-username",
"JENKINS_API_TOKEN": "your-api-token"
}
}
}
}Install
Add avisangle/jenkins-mcp-server to your client
No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.
Until then, follow the project's own README, or the setup the listing publishes under How to set it up.
Works with
What avisangle/jenkins-mcp-server connects to
No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.
Health and security
Is avisangle/jenkins-mcp-server looked after, and what do its setup files show
Health score
12 out of 100
| Part | Points | What we saw |
|---|---|---|
| Recent activity | 9.9 of 30 | Last push 255 days ago |
| Releases | 0 of 15 | 0 releases in 90 days |
| Issue replies | Not counted | The latest check has no issue response reading (fewer than 3 measured issues, or issues switched off) |
| Maintainer | 0 of 15 | Owned by a single user |
| Official source | 0 of 20 | Community server |
Sources
Where this comes from
- GitHubRegistry
A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.
Changelog
What changed
No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.
Get the free Developer’s Field Guide
A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.
Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.