mcp-jfrog and mcp-jetbrains
These are complements: the JFrog server enables artifact repository and build pipeline management within CI/CD workflows, while the JetBrains server provides IDE integration to access those pipelines and artifacts directly from development environments.
About mcp-jfrog
jfrog/mcp-jfrog
Model Context Protocol (MCP) Server for the JFrog Platform API, enabling repository management, build tracking, release lifecycle management, and more.
Implements 16+ MCP tools spanning artifact lifecycle management (AQL querying, repository CRUD), build and runtime visibility, and Xray vulnerability scanning—exposing JFrog's multi-product platform through a standardized protocol. Built as a TypeScript MCP server that communicates via stdio transport with AI clients, translating natural language requests into authenticated REST API calls against Artifactory, Xray, and other JFrog services. Integrates with Claude and other MCP-compatible AI assistants, enabling conversational access to DevOps workflows like repo creation, build tracking, and container image security auditing.
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