mcp-jenkins and mcp-jetbrains
These are **complements** — the Jenkins MCP server enables AI to interact with CI/CD pipelines while the JetBrains MCP server enables AI to interact with IDEs, so they work together to provide AI assistance across both development environments and deployment automation.
About mcp-jenkins
lanbaoshen/mcp-jenkins
The Model Context Protocol (MCP) is an open-source implementation that bridges Jenkins with AI language models following Anthropic's MCP specification. This project enables secure, contextual AI interactions with Jenkins tools while maintaining data privacy and security.
Exposes 20+ Jenkins operations as MCP tools—from querying jobs and builds to triggering builds and retrieving console output—while supporting multiple transport protocols (stdio, SSE, streamable-http) for integration with IDEs like VSCode and JetBrains. Implements optional read-only mode, configurable SSL verification, and session-based Jenkins client management to balance flexibility with security constraints in different deployment scenarios.
About mcp-jetbrains
JetBrains/mcp-jetbrains
A model context protocol server to work with JetBrains IDEs: IntelliJ, PyCharm, WebStorm, etc. Also, works with Android Studio
**Deprecated notice applies — this functionality is now built into IntelliJ-based IDEs 2025.2+.** This proxy server enabled external MCP clients (VS Code, Claude Desktop) to access IDE capabilities by proxying requests through a Node.js server to the IDE's built-in webserver, supporting multi-IDE scenarios via configurable host/port targeting. Architecture relied on stdio transport with environment-based configuration for host discovery and optional diagnostic logging.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work