MCP For Azure DevOps Boards
An MCP server that focuses on providing useful tools for Azure DevOps Boards
MCP for Azure DevOps Boards
A Model Context Protocol (MCP) server for interacting with Azure DevOps Boards and Work Items, written in Rust.
Features
-
Work Item Management: Create, update, get, and query work items.
-
Board Integration: List teams, boards, and fetch board items.
-
WIQL Support: Run custom WIQL queries.
-
Simplified Output: Optimized JSON output for LLM consumption (reduced token usage).
Installation
Check out the section MCP Configuration for how to configure your preferred AI (MCP) client.
macOS (Homebrew)
brew tap danielealbano/mcp-tools
brew install mcp-for-azure-devops-boards
The path to the binary will be /opt/homebrew/bin/mcp-for-azure-devops-boards.
Windows (Scoop)
scoop bucket add mcp-tools https://github.com/danielealbano/scoop-mcp-tools
scoop install mcp-for-azure-devops-boards
The path to the binary will be %USERPROFILE%\scoop\apps\mcp-for-azure-devops-boards\current\mcp-for-azure-devops-boards.exe.
Configuration
| Setting | Description | CLI Flag | Env Variable |
|---|---|---|---|
| Server Mode | Run as HTTP server instead of stdio | --server | N/A |
| Port | Port for HTTP server (default: 3000) | --port | N/A |
Note: If --server is not specified, the software will run in stdio mode.
Authentication
This server leverages standard Azure authentication mechanisms (like az or azd) to query Azure DevOps.
Installing Azure CLI
If you don't have the Azure CLI installed:
macOS (Homebrew):
brew install azure-cli
Windows (Scoop):
scoop install azure-cli
Windows (Chocolatey):
choco install azure-cli
For other installation methods, see the official Azure CLI installation guide.
Logging In
To authenticate, run:
az login
Usage
Stdio Mode (Default)
This is the standard mode for MCP clients (like Claude Desktop or Cursor). This mode is preferred for security as it ensures no credentials are shared over the network.
path/to/mcp-for-azure-devops-boards
HTTP Server Mode
You can also run it as an HTTP server (SSE). Note that in this mode, the server listens on 0.0.0.0 (all interfaces).
path/to/mcp-for-azure-devops-boards --server --port 3000
MCP Configuration
Note: Make sure you have run az login in your terminal so the process can pick up the credentials.
Quick setup with --install
The fastest way to register the MCP server with your preferred client:
mcp-for-azure-devops-boards --install <target>
Valid targets: claude-code, claude-desktop, cursor, vscode, codex, gemini-cli.
The command auto-detects the binary path, resolves the correct config file location, and writes the entry in the expected format. Existing configuration is preserved.
Manual configuration
Claude Code
Config file: ~/.claude.json
{
"mcpServers": {
"mcp-for-azure-devops-boards": {
"command": "/opt/homebrew/bin/mcp-for-azure-devops-boards"
}
}
}
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
Claude Desktop
Config file locations:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"mcp-for-azure-devops-boards": {
"command": "/opt/homebrew/bin/mcp-for-azure-devops-boards"
}
}
}
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
Cursor
Config file: ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-for-azure-devops-boards": {
"command": "/opt/homebrew/bin/mcp-for-azure-devops-boards"
}
}
}
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
VS Code
Config file: .vscode/mcp.json (workspace level)
{
"servers": {
"mcp-for-azure-devops-boards": {
"type": "stdio",
"command": "/opt/homebrew/bin/mcp-for-azure-devops-boards"
}
}
}
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
gemini-cli
Config file: ~/.gemini/settings.json
{
"mcpServers": {
"mcp-for-azure-devops-boards": {
"command": "/opt/homebrew/bin/mcp-for-azure-devops-boards"
}
}
}
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
Codex CLI
Config file: ~/.codex/config.toml
[mcp_servers.mcp-for-azure-devops-boards]
command = "/opt/homebrew/bin/mcp-for-azure-devops-boards"
Windows (Scoop): Replace the command path with
%USERPROFILE%\\scoop\\apps\\mcp-for-azure-devops-boards\\current\\mcp-for-azure-devops-boards.exe.
Available Tools
This software is currently in development. The tools and their parameters are subject to change.
The server exposes the following tools for MCP clients.
The general structure of the tool names is azdo_VERB_WHAT (e.g., azdo_list_teams, azdo_get_work_item).
Discovery
azdo_list_organizations: List all Azure DevOps organizations the authenticated user has access to.- Required: None (uses authenticated user's credentials)
azdo_list_projects: List all projects in an Azure DevOps organization.- Required:
organization
- Required:
Work Items
Note: All work item tools require
organizationandprojectparameters.
azdo_create_work_item: Create a new work item.- Required:
organization,project,work_item_type,title - Optional:
description,assigned_to,area_path,iteration_path,state,board_column,board_row,priority,severity,story_points,effort,remaining_work,tags,activity,parent_id,start_date,target_date,acceptance_criteria,repro_steps,fields(JSON string for custom fields).
- Required:
azdo_update_work_item: Update an existing work item.- Required:
organization,project,id - Optional: All fields available in creation.
- Required:
azdo_get_work_item: Get details of a specific work item.- Required:
organization,project,id - Optional:
include_latest_n_comments(number of recent comments to include, -1 for all)
- Required:
azdo_get_work_items: Get multiple work items by their IDs.- Required:
organization,project,ids(array of work item IDs) - Optional:
include_latest_n_comments(number of recent comments to include, -1 for all)
- Required:
azdo_query_work_items: Query work items using structured filters.- Required:
organization,project - Optional Filters:
area_path,iteration_path,created_date_from/to,modified_date_from/to. - Inclusion Lists:
include_board_column,include_board_row,include_work_item_type,include_state,include_assigned_to,include_tags. - Exclusion Lists:
exclude_board_column,exclude_board_row,exclude_work_item_type,exclude_state,exclude_assigned_to,exclude_tags. - Optional:
include_latest_n_comments(number of recent comments to include, -1 for all)
- Required:
azdo_query_work_items_by_wiql: Execute a raw WIQL (Work Item Query Language) query.- Required:
organization,project,query - Optional:
include_latest_n_comments(number of recent comments to include, -1 for all)
- Required:
azdo_add_comment: Add a comment to a work item.- Required:
organization,project,work_item_id,text
- Required:
azdo_link_work_items: Create a relationship between two work items.- Required:
organization,project,source_id,target_id,link_type(Parent, Child, Related, Duplicate, Dependency).
- Required:
Boards & Teams
Note: All board and team tools require
organizationandprojectparameters.
azdo_list_teams: List all teams in the project.- Required:
organization,project
- Required:
azdo_get_team: Get details of a specific team.- Required:
organization,project,team_id
- Required:
azdo_list_team_boards: List boards for a specific team.- Required:
organization,project,team_id
- Required:
azdo_get_team_board: Get details of a specific board.- Required:
organization,project,team_id,board_id
- Required:
azdo_list_work_item_types: List all available work item types in the project.- Required:
organization,project
- Required:
azdo_list_tags: List all tags in use in the project.- Required:
organization,project
- Required:
azdo_get_team_current_iteration: Get the current active iteration/sprint for a team.- Required:
organization,project,team_id
- Required:
azdo_get_team_iterations: Get all iterations/sprints for a team.- Required:
organization,project,team_id
- Required:
Contributing
We welcome contributions!
- Fork the repository.
- Create a new branch for your feature or bugfix (
git checkout -b feature/amazing-feature). - Commit your changes.
- Push to your branch.
- Open a Pull Request.
Building from Source
Prerequisites
Steps
-
Clone the repository:
git clone https://github.com/danielealbano/mcp-for-azure-devops-boards.git cd mcp-for-azure-devops-boards -
Build the project:
cargo build --release
Tooling
- Run tests:
cargo test - Check code style:
cargo fmt --check - Linting:
cargo clippy
Disclaimer
This project is not affiliated with, endorsed by, or sponsored by Microsoft. Azure, Azure DevOps, and related trademarks are the property of their respective owners. This software uses standard Microsoft's services APIs to interact with Azure and Microsoft Graph, among other services.
License
This project is licensed under the MIT License - see the LICENSE.md file for details.
관련 서버
Alpha Vantage MCP Server
스폰서Access financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
C++ Core Guidelines
Enforce consistent C++ style and best practices across your codebase. Analyze naming conventions, memory safety, and const correctness, and get actionable modernization suggestions up to C++23. Accelerate reviews with ready-made prompts and quick access to curated guidelines.
Octomind
Create and manage end-to-end tests using the Octomind platform.
RepoRecall
Zero-tool-call codebase intelligence for Claude Code and MCP clients. Automatically injects the right code context, functions, callers, and call chains, before the LLM starts thinking. Replaces 4-6 grep/read round-trips with a single 5ms hook injection, cutting token usage by 3-8x.
Comet Opik
Query and analyze your Opik logs, traces, prompts and all other telemtry data from your LLMs in natural language.
BCMS MCP
Give me a one - two sentence description of the BCMS MCP # MCP The BCMS Model Context Protocol (MCP) integration enables AI assistants like Claude, Cursor, and other MCP-compatible tools to interact directly with your BCMS content. This allows you to create, read, and update content entries, manage media files, and explore your content structure—all through natural language conversations with AI. ## What is MCP? The [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) is an open standard developed by Anthropic that allows AI applications to securely connect to external data sources and tools. With BCMS MCP support, you can leverage AI assistants to: - Query and explore your content structure - Create new content entries with AI-generated content - Update existing entries - Manage your media library - Get intelligent suggestions based on your content model --- ## Getting Started ### Prerequisites 1. A BCMS account with an active instance 2. An MCP key with appropriate permissions 3. An MCP-compatible client (Claude Desktop, Cursor, or any MCP client) ### Step 1: Create an MCP Key 1. Navigate to your BCMS dashboard 2. Go to Settings → MCP 3. Click Create MCP Key 4. Configure the permissions for templates you want the AI to access:GET: Read entries 5. POST: Create entries 6. PUT: Update entries 7. DELETE: Delete entries Note: Right now, MCP only supports creating, reading and updating content. ### Step 2: Configure Your MCP Client You can find full instructions for integrating BCMS with your AI tools right inside BCMS, on the MCP page. But in general, installing BCMS MCP works in a standard way: ``` { "mcpServers": { "bcms": { "url": "https://app.thebcms.com/api/v3/mcp?mcpKey=YOUR_MCP_KEY" } } } ``` ## Available Tools Once connected, your AI assistant will have access to the following tools based on your MCP key permissions: ### Content Discovery #### list_templates_and_entries Lists all templates and their entries that you have access to. This is typically the first tool to call when exploring your BCMS content. Returns: - Template IDs, names, and slugs - Entry IDs with titles and slugs for each language Example prompt: "Show me all the templates and entries in my BCMS" --- ### Entry Management #### list_entries_for_{templateId} Retrieves all entries for a specific template with full content data. A separate tool is generated for each template you have access to. Returns: - Complete entry data including all meta fields - Content in all configured languages - Entry statuses Example prompt: "List all blog posts from my Blog template" --- #### create_entry_for_{templateId} Creates a new entry for a specific template. The input schema is dynamically generated based on your template's field structure. Input: - statuses: Array of status assignments per language - meta: Array of metadata for each language (title, slug, custom fields) - content: Array of content nodes for each language Example prompt: "Create a new blog post titled 'Getting Started with BCMS' with a brief introduction paragraph" --- #### update_entry_for_{templateId} Updates an existing entry for a specific language. Input: - entryId: The ID of the entry to update - lng: Language code (e.g., "en") - status: Optional status ID - meta: Updated metadata - content: Updated content nodes Example prompt: "Update the introduction paragraph of my 'Getting Started' blog post" --- ### Media Management #### list_all_media Lists all media files in your media library. Returns: - Media IDs, names, and types - File metadata (size, dimensions for images) - Parent directory information Example prompt: "Show me all images in my media library" --- #### list_media_dirs Lists the directory structure of your media library. Returns: - Hierarchical directory structure - Directory IDs and names Example prompt: "Show me the folder structure of my media library" --- #### create-media-directory Creates a new directory in your media library. Input: - name: Name of the directory - parentId: Optional parent directory ID (root if not specified) Example prompt: "Create a new folder called 'Blog Images' in my media library" --- #### request-upload-media-url Returns a URL you use to upload a file (for example via POST with multipart form data), which avoids pushing large binaries through the MCP tool payload. You still need a valid file name and MIME type when uploading, as described in the tool response. Availability: Only when the MCP key has Can mutate media enabled. Example prompt: “Give me an upload URL for a new hero image, then tell me how to upload it.” Input: - fileName: Name of the file with extension - fileData: Base64-encoded file data (with data URI prefix) - parentId: Optional parent directory ID Example prompt: "Upload this image to my Blog Images folder" --- ### Linking Tools #### get_entry_pointer_link Generates an internal BCMS link to an entry for use in content. Input: - entryId: The ID of the entry to link to Returns: - Internal link format: entry:{entryId}@*_{templateId}:entry Example prompt: "Get me the internal link for the 'About Us' page entry" --- #### get_media_pointer_link Generates an internal BCMS link to a media item for use in content. Input: - mediaId: The ID of the media item Returns: - Internal link format: media:{mediaId}@*_@*_:entry Example prompt: "Get the link for the hero image so I can use it in my blog post" --- ## Content Structure ### Entry Content Nodes When creating or updating entries, content is structured as an array of nodes. Supported node types include: Type Description paragraph Standard text paragraph heading Heading (h1-h6) bulletList Unordered list orderedList Numbered list listItem List item codeBlock Code block with syntax highlighting blockquote Quote block image Image node widget Custom widget with props ### Example Content Structure ``` { "content": [ { "lng": "en", "nodes": [ { "type": "heading", "attrs": { "level": 1 }, "content": [ { "type": "text", "text": "Welcome to BCMS" } ] }, { "type": "paragraph", "content": [ { "type": "text", "text": "This is your first paragraph." } ] } ] } ] } ``` ## Security & Permissions ### MCP Key Scopes Your MCP key controls what the AI can access: - Template Access: Only templates explicitly granted in the MCP key are visible - Operation Permissions: Each template can have independent GET/POST/PUT/DELETE permissions - Media Access: Media operations are controlled separately ### Best Practices 1. Principle of Least Privilege: Only grant the permissions needed for your use case 2. Separate Keys: Create different MCP keys for different purposes or team members 3. Regular Rotation: Periodically rotate your MCP keys ## Use Cases ### Content Creation Workflows Blog Post Creation "Create a new blog post about the benefits of headless CMS. Include an introduction, three main benefits with explanations, and a conclusion. Use the Blog template." Product Updates "Update the price field for all products in the Electronics category to apply a 10% discount" ### Content Exploration Content Audit "List all blog posts that don't have a featured image set" Translation Status "Show me which entries are missing German translations" ### Media Organization Library Cleanup "Show me all unused images in the media library" Folder Setup "Create folder structure for: Products > Categories > Electronics, Clothing, Home" ## Troubleshooting ### Common Issues #### "MCP key not found" - Verify your MCP key format: keyId.keySecret.instanceId - Ensure the MCP key hasn't been deleted or deactivated - Check that you're using the correct instance #### "MCP key does not have access to template" - Review your MCP key permissions in the dashboard - Ensure the required operation (GET/POST/PUT/DELETE) is enabled for the template #### Session Expired - MCP sessions may timeout after periods of inactivity - Simply start a new conversation to establish a fresh session ### Getting Help - Documentation: [thebcms.com/docs](https://thebcms.com/docs) - Support: [[email protected]](mailto:[email protected]) - Community: [Join BCMS Discord](https://discord.com/invite/SYBY89ccaR) for community support ## Technical Reference ### Endpoint POST https://app.thebcms.com/api/v3/mcp?mcpKey={MCP_KEY} ### Transport BCMS MCP uses the Streamable HTTP transport with session management. Sessions are maintained via the mcp-session-id header. ### Response Format All tools return structured JSON responses conforming to the MCP specification with: - content: Array of content blocks - structuredContent: Typed response data ## Rate Limits MCP requests are subject to the same rate limits as API requests: - Requests are tracked per MCP key - Contact support if you need higher limits for production workloads
MCP Tools
A developer toolset for creating a real-time MCP server using the PHP Laravel framework, with GitHub integration.
Google Tag Manager
Integrates Google Tag Manager to automate GTM configuration and component creation through natural language prompts.
Jetty.io
Work on dataset metadata with MLCommons Croissant validation and creation.
PromptEasy.EU
The first EU-sovereign, version-controlled prompt library that natively exposes your team’s templates as a managed MCP Server for agentic discovery.
Testomat.io
Integrate Testomat.io API with AI assistants for test management.