Add support for Docker image MCP server

[ArkadiuszMakosa]

I would like to use Devops MCP server containerized, so all dependencies like NodeJs would be not needed anymore.

Summary

Add dockerfile and contenerize current sollution

Tools

Docker

Docker installation will be needed to build image and publish it to repository.

Docker repository

It would be nice, to have some dedicated image repository haveing build image, ready to pull and run locally

Rules

1. Add dockerfile with all steps needed to create MCP serwer in docker image
2. Modify pipeline to build image
3. Publish docker image to known docker image repository

Special treat

If you follow the rules, you'll get candy!

[danhellem]

@ArkadiuszMakosa please refrain from creating a PR untill the issue has been reviewed and approved

[Novaes]

Thanks for the contribution, @ArkadiuszMakosa.

We’ll re-discuss internally this topic, whether this is a direction we want to now pursue — FYI. @kboom / @aaudzei.

In the meantime, a valuable contribution would be a documentation page with instructions for adapting the existing https://github.com/microsoft/azure-devops-mcp/blob/main/.devcontainer/devcontainer.json for Docker usage with minimal changes. This could support future publishing to https://mcr.microsoft.com/en-us/catalog if aligned with our roadmap.

Helpful resources:

• https://microsoft.github.io/code-with-engineering-playbook/developer-experience/devcontainers-getting-started/
• https://microsoft.github.io/code-with-engineering-playbook/developer-experience/devcontainers-going-further/
• https://code.visualstudio.com/docs/devcontainers/containers

Note: We operate a local MCP server using stdio as transport.

[yevheniilavrenchuk]

In the meantime, a valuable contribution would be a documentation page with instructions for adapting the existing https://github.com/microsoft/azure-devops-mcp/blob/main/.devcontainer/devcontainer.json for Docker usage with minimal changes. This could support future publishing to https://mcr.microsoft.com/en-us/catalog if aligned with our roadmap.

Hi @Novaes I'm wondering if it was tested and actually working? It is asking to authenticate to Azure Cloud with machine code, etc. Is there a way to provide my locally authenticated session?

I'm also curious how @ArkadiuszMakosa managed to remediate an authentication issue, when hosting in Docker container. I'm actually facing the same issue - first request to MCP server asks about authentication. Since it is docker container and there is no adequate way to open interactive session to get authenticated using the browser (how it works locally), so it fails to run.

Thank you in advance.

[ArkadiuszMakosa]

Thank you for including me in this discussion. Regarding the Docker implementation, my initial pull request was more of a preliminary exploration, raising several questions rather than providing definitive answers. My intention was to develop the Docker functionality with your team's assistance. Unfortunately, my current schedule does not permit me to dedicate time to this until January of next year. Therefore, if no one else addresses this feature in the interim, I will reach out in January to continue working on it. Thanks, Arkadiusz

…

On Thu, Oct 16, 2025, 1:29 PM yevheniilavrenchuk ***@***.***> wrote: *yevheniilavrenchuk* left a comment (microsoft/azure-devops-mcp#538) <#538 (comment)> In the meantime, a valuable contribution would be a documentation page with instructions for adapting the existing https://github.com/microsoft/azure-devops-mcp/blob/main/.devcontainer/devcontainer.json for Docker usage with minimal changes. This could support future publishing to https://mcr.microsoft.com/en-us/catalog if aligned with our roadmap. Hi @Novaes <https://github.com/Novaes> I'm wondering if it was tested and actually working? For me it is failing with requirement to authenticate to Azure Cloud. I'm also curious how @ArkadiuszMakosa <https://github.com/ArkadiuszMakosa> managed to remediate an authentication issue, when hosting in Docker container. I'm actually facing the same issue - first request to MCP server asks about authentication. Since it is docker container and there is no adequate way to open interactive session to get authenticated using the browser (how it works locally), so it fails to run. Thank you in advance. — Reply to this email directly, view it on GitHub <#538 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADXMSKYMLDJQVSB43VV47AT3X56SLAVCNFSM6AAAAACH2COGW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJQGQZDMMBUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ftrjc]

I was playing around while performing an evaluation of Cursor - And I was running into similar issues where I wanted to have the Microsoft Azure Devops MCP Server

1. centrally hosted in a docker container
2. Support streamable-http
3. Multi-User Tenancy, where the users can pass the token and settings via headers.

I just successfully got it working locally in cursor, Next test is to package it up as a docker image so I can host it in my cluster to test.

If it helps anyone - here is my branch: https://github.com/ftrjc/azure-devops-mcp/tree/multi-tenant

I connect from cursor with something like this:

"azdevops": {
"type": "http",
"url": "http://127.0.0.1:3000/mcp",
"headers": {
"Authorization": "Token MY_AZ_PAT_TOKEN",
"x-azure-org": "My Org"
}
}

[danhellem]

I was playing around while performing an evaluation of Cursor - And I was running into similar issues where I wanted to have the Microsoft Azure Devops MCP Server

1. centrally hosted in a docker container
2. Support streamable-http
3. Multi-User Tenancy, where the users can pass the token and settings via headers.

I just successfully got it working locally in cursor, Next test is to package it up as a docker image so I can host it in my cluster to test.

If it helps anyone - here is my branch: https://github.com/ftrjc/azure-devops-mcp/tree/multi-tenant

I connect from cursor with something like this:

"azdevops": { "type": "http", "url": "http://127.0.0.1:3000/mcp", "headers": { "Authorization": "Token MY_AZ_PAT_TOKEN", "x-azure-org": "My Org" } }

Using PATs are not recommended