MCP Server DevOps Bridge

A Model Context Protocol (MCP) server that enables Claude to bridge and orchestrate your DevOps toolchain through natural language. Stop context-switching between tools - let Claude handle the integration seamlessly.

🌉 Bridge Your DevOps Tools

Connect your essential DevOps platforms:

• Azure DevOps - Work items, wiki, sprints
• GitHub - Pull requests, code reviews, repositories
• Slack - Team communication, notifications, updates

🎯 Key Benefits

• Natural Language Interface - No need to learn different APIs or CLI tools
• Cross-Platform Integration - Work items link to PRs, PRs trigger notifications
• Unified Workflow - Let Claude handle the context switching between tools
• Flexible Architecture - Easy to extend with new integrations

🚀 Getting Started

Prerequisites

• Go 1.23 or later
• Access tokens for your platforms:
  • Azure DevOps PAT
  • GitHub PAT (optional)
  • Slack Bot Token (optional)

Installation

1. Clone and build:

git clone https://github.com/yourusername/mcp-server-devops-bridge
cd mcp-server-devops-bridge
go build

2. Configure your environment:

export AZURE_DEVOPS_ORG="your-org"
export AZDO_PAT="your-pat-token"
export AZURE_DEVOPS_PROJECT="your-project"

# Optional integrations
export GITHUB_PAT="your-github-pat"
export SLACK_BOT_TOKEN="your-slack-token"
export DEFAULT_SLACK_CHANNEL="some-slack-channel-id"

3. Add to Claude’s configuration:

{
  "mcpServers": {
    "wcgw": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "--from",
        "wcgw@latest",
        "--python",
        "3.12",
        "wcgw_mcp"
      ]
    },
    "devops-bridge": {
      "command": "/full/path/to/mcp-server-devops-bridge/mcp-server-devops-bridge",
      "args": [],
      "env": {
        "AZURE_DEVOPS_ORG": "organization",
        "AZDO_PAT": "personal_access_token",
        "AZURE_DEVOPS_PROJECT": "project",
        "SLACK_DEFAULT_CHANNEL": "channel_id",
        "SLACK_BOT_TOKEN": "bot_token",
        "GITHUB_PAT": "personal_access_token",
        "OPENAI_API_KEY": "openaikey",
        "QDRANT_URL": "http://localhost:6333",
        "QDRANT_API_KEY": "yourkey",
        "NEO4J_URL": "yourneo4jinstance",
        "NEO4J_USER": "neo4j",
        "NEO4J_PASSWORD": "neo4jpassword"
      }
    }
  }
}

In this configuration I added wcgw_mcp, because this will technically allow you to ask Claude (or which ever client you use) to directly fix your code as well, but this is untested at the moment. In any case it will also allow you to ask Claude to check you code-bases and use it as context when creating work items in Azure DevOps.

💡 Example Workflows

Cross-Platform Task Management

"Create a user story for the new authentication feature, link it to the existing GitHub PR #123, and notify the team in Slack"

Code Review Workflow

"Find all work items related to authentication, show their linked PRs, and summarize recent code review comments"

Status Reporting

"Generate a sprint report including:
- Work item status from Azure Boards
- PR review status from GitHub
- Team discussions from Slack"

Documentation Management

"Update the wiki page for authentication and link it to relevant work items and PRs"

🔌 Supported Integrations

Azure DevOps

• Work item management (any field supported)
• Wiki documentation
• Sprint planning
• Attachments and discussions

GitHub

• PR management and reviews
• Code search and navigation
• Repository management
• Review comments

Slack

• Rich message formatting
• Thread management
• Notifications
• Team coordination

🛠 Architecture

The bridge uses the Model Context Protocol to provide Claude with structured access to your DevOps tools. This enables:

• Type-safe operations
• Proper error handling
• Clear feedback
• Extensible design

🤝 Contributing

We welcome contributions! Key areas for enhancement:

• Additional platform integrations (GitLab, Jira, etc.)
• Enhanced cross-platform workflows
• Improved reporting capabilities
• New integration patterns

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

🔒 Security

• Store access tokens securely
• Grant minimal required permissions
• Regularly rotate credentials
• Audit integration access

🆘 Support

• Open an issue for bugs or feature requests
• Check discussions for common questions
• Review wiki for implementation guides

Features

Azure DevOps Integration

• Work Item Management
  • Create, update, and query work items
  • Add/remove tags
  • Manage work item attachments
  • Add comments and track discussions
  • Create work items from templates
  • Manage work item relationships
• Wiki Management
  • Create and update wiki pages
  • Search wiki content
  • Retrieve page content and subpages
• Sprint Management
  • Query current and upcoming sprints
  • Track sprint progress

GitHub Integration

• Pull Request Management
  • List open/closed pull requests
  • Get detailed PR information
• Code Search
  • Search across repositories
  • Filter by path, language, and repository

Slack Integration

• Message Formatting
  • Format messages using Block Kit
  • Support for headers, sections, and context blocks
• Message Search
  • Search message history
  • Filter by channel and user
• Message Posting
  • Post messages to channels
  • Support for threaded replies
  • Rich message formatting with blocks

N8N Integration

• Workflow Management
  • List workflows
  • Create new workflows
  • Toggle workflow activation
  • Monitor workflow executions
• Workflow Templates
  • Format workflow configurations
  • Support for various node types
  • Automated connection setup

Memory Management

• Vector Storage (Qdrant)
  • Semantic search capabilities
  • Document storage with metadata
  • Similarity search with configurable thresholds
• Graph Database (Neo4j)
  • Store relationships between memories
  • Query using Cypher
  • Track temporal relationships

AI Integration

• Claude Integration
  • Direct chat capabilities
  • Memory-augmented conversations
  • Context-aware responses
• OpenAI Integration
  • GPT-4 integration
  • Memory retrieval and formatting
  • Structured output generation

Cross-Integration Features

• Status Report Generation
  • Combine data from multiple sources
  • Sprint status reports
  • Work item summaries
  • PR status integration
• Work Item Reminders
  • Slack notifications
  • Customizable messages
  • Automated tracking
• Standup Report Generation
  • Team-based reporting
  • State-grouped work items
  • Rich Slack formatting

In some cases you will not have access to the environment, so create a start.sh and make it executable, so you can wrap the environment.

#!/bin/bash

# Azure DevOps Configuration
export AZURE_DEVOPS_ORG="YOUR ORG"
export AZDO_PAT="YOUR PAT"
export AZURE_DEVOPS_PROJECT="YOUR PROJECT"

# GitHub Configuration
export GITHUB_PAT="YOUR PAT"

# Slack Configuration
export SLACK_BOT_TOKEN="YOUR TOKEN"
export DEFAULT_SLACK_CHANNEL="YOUR CHANNEL ID"

# N8N Configuration
export N8N_BASE_URL="http://localhost:5678"
export N8N_API_KEY="YOUR API KEY"

# OpenAI Configuration
export OPENAI_API_KEY="YOUR API KEY"

# Qdrant Configuration
export QDRANT_URL="http://localhost:6333"
export QDRANT_API_KEY="your-qdrant-api-key"

# Neo4j Configuration
export NEO4J_URL="http://localhost:7474"
export NEO4J_USER="neo4j"
export NEO4J_PASSWORD="your-neo4j-password"

# Email Configuration (if using email features)
export EMAIL_INBOX_WEBHOOK_URL="YOUR WEBHOOK URL"
export EMAIL_SEARCH_WEBHOOK_URL="YOUR WEBHOOK URL"
export EMAIL_REPLY_WEBHOOK_URL="YOUR WEBHOOK URL"

/path/to/mcp-server-devops-bridge/mcp-server-devops-bridge