What integrations does MCP DevOps Hub support?
It integrates with Jira, GitHub, CI/CD pipelines, Slack, Microsoft Teams, and Groq AI for code analysis.
@SBDI
Basic information
MCP server for end-to-end development visibility (Jira, GitHub, CI/CD, etc.)
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
MCP DevOps Hub is an MCP server that provides end-to-end development visibility by integrating with Jira, GitHub, CI/CD pipelines, team notification tools, and Groq AI for code analysis. It is designed for development and DevOps teams who want a centralized view of their workflows.
Install dependencies by running scripts\setup-dev.bat, then copy .env.example to .env and configure your environment variables with the required API keys. Finally, run the server with the command mcp-devops-hub.
It integrates with Jira, GitHub, CI/CD pipelines, Slack, Microsoft Teams, and Groq AI for code analysis.
Run `scripts\setup-dev.bat` to install dependencies, configure your `.env` file with the required API keys, then start the server with `mcp-devops-hub`.
Yes, each integrated service (Jira, GitHub, Slack, MS Teams, Groq AI) needs its own API keys or tokens. Setup details are provided in the `.env.example` file.

Free MCP server for software end-of-life intelligence: EOL dates, support status, and the 0-100 EOL Risk Score across 480+ tracked products. Agents can check a single version, pull a product's full lifecycle schedule, or
Query your team's drift, vulnerability, and migration data from any AI assistant. Vibgrate MCP connects Cursor, Claude, ChatGPT, Windsurf, or VS Code to Vibgrate Cloud: 51 tools for DriftScores, CVEs and EOL runtimes, up

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
Comments