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.
Connect your essential DevOps platforms:
git clone https://github.com/yourusername/mcp-server-devops-bridge
cd mcp-server-devops-bridge
go build
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"
{
"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.
"Create a user story for the new authentication feature, link it to the existing GitHub PR #123, and notify the team in Slack"
"Find all work items related to authentication, show their linked PRs, and summarize recent code review comments"
"Generate a sprint report including:
- Work item status from Azure Boards
- PR review status from GitHub
- Team discussions from Slack"
"Update the wiki page for authentication and link it to relevant work items and PRs"
The bridge uses the Model Context Protocol to provide Claude with structured access to your DevOps tools. This enables:
We welcome contributions! Key areas for enhancement:
This project is licensed under the MIT License - see the LICENSE file for details.
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
Ragdocs
MCP server for RAG-based document search and management
Systemprompt Mcp Gmail
A specialized Model Context Protocol (MCP) server that enables you to search, read, delete and send emails from your Gmail account, leveraging an AI Agent to help with each operation. Optimized for Systemprompt MCP Voice client.
Base Mcp
A Model Context Protocol (MCP) server that provides onchain tools for LLMs, allowing them to interact with the Base network and Coinbase API.
