Azure DevOps
Integrate with Azure DevOps services to manage work items, repositories, and pipelines.
Azure DevOps MCP Server
This Model Context Protocol (MCP) server provides integration with Azure DevOps, allowing Claude Desktop/Cline to interact with Azure DevOps services.
Prerequisites
- Node.js (v20 LTS or higher)
- npm (comes with Node.js)
- An MCP compatible client
- Azure DevOps account with access tokens
Installation
Installing via Smithery
To install Azure DevOps Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @RainyCodeWizard/azure-devops-mcp-server --client claude
Manual Installation
- Clone this repository:
git clone https://github.com/RainyCodeWizard/azure-devops-mcp-server.git
cd azure-devops-mcp-server
- Install dependencies:
npm install
- Build the server:
npm run build
Note: The build output (build/ directory) is not included in version control. You must run the build command after cloning the repository.
Configuration
1. Get Azure DevOps Personal Access Token (PAT)
- Go to Azure DevOps and sign in
- Click on your profile picture in the top right
- Select "Security"
- Click "New Token"
- Give your token a name and select the required scopes:
Code (read, write)- For Pull Request operationsWork Items (read, write)- For Work Item managementBuild (read, execute)- For Pipeline operationsWiki (read, write)- For Wiki operationsProject and Team (read)- For Project and Board information
- Copy the generated token
2. Configure MCP Settings for Client Apps
Add the server configuration to your Cline MCP settings file:
- For Cline VSCode extension:
%APPDATA%/Code/User/globalStorage/rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json - For Claude desktop app:
%LOCALAPPDATA%/Claude/claude_desktop_config.json
Add the following configuration to the mcpServers object:
{
"mcpServers": {
"azure-devops": {
"command": "node",
"args": ["/absolute/path/to/azure-devops-server/build/index.js"],
"env": {
"AZURE_DEVOPS_ORG": "your-organization",
"AZURE_DEVOPS_PAT": "your-personal-access-token",
"AZURE_DEVOPS_PROJECT_ID": "your-project-id"
},
"disabled": false,
"autoApprove": []
}
}
}
Replace the following values:
/absolute/path/to/azure-devops-server: The absolute path to where you cloned this repositoryyour-organization: Your Azure DevOps organization nameyour-project-id: Your Azure DevOps project IDyour-personal-access-token: The PAT you generated in step 1
Available Tools
Work Items
get_work_item: Get a work item by IDlist_work_items: Query work items using WIQLcreate_work_item: Create a new work item (Bug, Task, User Story)update_work_item: Update an existing work item
Boards
get_boards: Get available boards in the project
Git
list_repositories: List all Git repositories in the project- Returns: List of repositories with ID, name, default branch, size, and URLs
get_file: Get the content of a specific file from the repository- Parameters:
repositoryId: ID of the repositorypath: Path to the file in the repository (e.g., "src/index.ts")branch: Branch name to get the file from (optional, defaults to main)version: Specific version (commit ID) to get the file from (optional)
- Returns: File content with metadata including:
- File path
- File size
- File content
- Last commit ID
- Last modified date
- Parameters:
compare_branches: Compare two branches and get commit history between them- Parameters:
repositoryId: ID of the repository to compare branches insourceBranch: Source branch name (e.g., "develop")targetBranch: Target branch name (e.g., "main")maxCommits: Maximum number of commits to return (optional, defaults to 100)historyMode: Git history mode to use (optional, defaults to "simplified")simplified: Standard git log behavior (default)first-parent: Only show first parent of merge commitsfull: Show all commits including merge commitsfull-simplify-merges: Show all commits but simplify merge history
includeDetails: Include detailed commit information (optional, defaults to false)- When true, includes:
- Full commit message
- List of changed files with:
- File path
- Change type (add, edit, delete)
- Number of lines added/deleted
- When true, includes:
- Returns: List of commits with commit ID, author, date, and message
- Parameters:
Pipelines
list_pipelines: List all pipelines in the projecttrigger_pipeline: Execute a pipeline
Pull Requests
list_pull_requests: List pull requestscreate_pull_request: Create a new pull requestupdate_pull_request: Update a pull requestget_pull_request: Get pull request details
Wiki
get_wikis: List all wikis in the projectget_wiki_page: Get a wiki pagecreate_wiki: Create a new wikiupdate_wiki_page: Create or update a wiki page
Projects
list_projects: List all projects in the Azure DevOps organization
Verification
- Restart Cline (or VSCode) after adding the configuration
- The Azure DevOps MCP server should now be listed in Cline's capabilities
- You can verify the installation using the MCP Inspector:
npm run inspector
Troubleshooting
-
If the server isn't connecting:
- Check that the path in your MCP settings is correct
- Verify your Azure DevOps credentials
- Check the Cline logs for any error messages
-
If you get authentication errors:
- Verify your PAT hasn't expired
- Ensure the PAT has all necessary scopes
- Double-check the organization and project ID
-
For other issues:
- Run the inspector tool to verify the server is working correctly
- Check the server logs for any error messages
Development
To modify or extend the server:
- Make your changes in the
srcdirectory - Run
npm run watchfor development - Build with
npm run buildwhen ready - Test using the inspector:
npm run inspector
License
MIT License - See LICENSE for details
Máy chủ liên quan
Alpha Vantage MCP Server
nhà tài trợAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
YAPI MCP Server
An MCP server for accessing YAPI interface details, configured via environment variables.
Remote MCP Server on Cloudflare
An example of a remote MCP server deployable on Cloudflare Workers, without authentication.
MCP Server Pentest
Automated browser penetration testing to detect XSS and SQL vulnerabilities.
Ghost MCP
An MCP server for the Ghost blogging platform with Server-Sent Events (SSE) support.
MCP Feedback Enhanced
An MCP server for interactive user feedback and command execution in AI-assisted development, supporting both Web and Desktop interfaces.
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
Liana-MCP
A natural language interface for cell-cell communication analysis using the Liana framework.
MCPHost
A CLI host application that enables Large Language Models (LLMs) to interact with external tools through the Model Context Protocol (MCP).
Photon
A TypeScript framework that turns a single class into an MCP server, CLI tool, and web dashboard with a marketplace of 35 ready-made photons.
Node.js Sandbox MCP Server
Run arbitrary JavaScript in an isolated Docker container with on-the-fly npm dependency installation.