iTranslated by AI
Setting up GitHub MCP Server with Docker Desktop for use in Cline
Docker Desktop includes a convenient tool called the MCP Toolkit that allows for centralized management of MCPs. However, when setting up the GitHub MCP Server via the MCP Toolkit, a 404 error is returned despite the LLM successfully sending requests, as described in the following issue:
Therefore, in this post, I will walk through how to set up the GitHub MCP Server directly from Docker Hub on Docker Desktop, bypassing the MCP Toolkit, and configure it to be used with Cline.
Configuration
- Windows 11 Pro 25H2
- Docker Desktop
- acuvity/mcp-server-github
- Docker Desktop
Searching and Pulling mcp-server-github from Docker Hub
Since you need to edit the Environment variables before starting, select Pull instead of Run here.
Selecting from Images and Running
Set arbitrary values for the container name and port, and enter the access token generated on the GitHub website as the Value for the GITHUB_PERSONAL_ACCESS_TOKEN variable under Environment variables.
You can generate an access token from the following page:
Generating it as a Personal access token (classic) with repo permissions should be sufficient at a minimum.
Once you have finished entering the required items, click Run to start the GitHub MCP Server.
Cline Configuration
Click the MCP Servers button in Cline and specify Remote Servers.
In Server Name, specify the URL and port number of the server you just set up, and append /mcp to the end.
For Transport Type, select Streamable HTTP and click Add Server.
That is all.
While the fact that it could not be handled by the Docker MCP Toolkit was a sticking point, it might have been the optimal solution to set up the server directly anyway, as it can be difficult to manage when mixed in with other tools.
Discussion