
MCP Secure Installer
Automatically installs and containerizes MCP servers from GitHub repositories using MCP sampling to analyze repositories and create appropriate Docker images.
README
MCP Secure Installer (mcp-sinstaller
)
This project provides an MCP server installer that can automatically install, and containerize other MCP servers from GitHub repositories. It uses the Model Context Protocol (MCP) sampling feature to analyze repositories and create appropriate docker images.
https://github.com/user-attachments/assets/6ad17a8b-c88f-4cba-abea-3a1f5288ed3c
Requirements
- Docker
- MCP Client with Sampling enabled
Enable Sampling in VS Code Insiders (Recommended)
Add the following to your VS code settings:
"chat.mcp.serverSampling": {
"Global in Code - Insiders: sampling": {
"allowedDuringChat": true
}
}
Usage
Running the Server in VS Code (Recommended)
- uvx
First, clone the repository:
git clone https://github.com/semcp/mcp-sinstaller.git
Then, add the following to your VS Code settings:
"mcp-sinstaller": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"/path/to/mcp-sinstaller",
"python",
"/path/to/mcp-sinstaller/mcp_installer.py",
]
},
Server Naming & Multiple Servers
The installer uses a structured naming scheme: owner-repo-servername
to avoid conflicts when installing multiple servers from the same repository.
Examples:
https://github.com/modelcontextprotocol/servers/tree/main/src/fetch
→modelcontextprotocol-servers-fetch
https://github.com/modelcontextprotocol/servers/tree/main/src/filesystem
→modelcontextprotocol-servers-filesystem
https://github.com/github/github-mcp-server
→github-github-mcp-server
This allows you to install multiple MCP servers from repositories like modelcontextprotocol/servers
without naming conflicts.
Example (GitHub MCP Server)
Prompt: "install https://github.com/github/github-mcp-server"
GitHub Copilot:
I'll install the GitHub MCP server from the repository you specified.
sampling (MCP Server):
Input:
{
"url": "https://github.com/github/github-mcp-server"
}
Output:
Successfully built Docker image for MCP server 'github-mcp-server'!
Repository: https://github.com/github/github-mcp-server
Location: /Users/mossaka/.mcp-installer/servers/github-mcp-server
DOCKER IMAGE:
- Using existing Dockerfile
- Image: mcp-installer-github-mcp-server
- Size & Created: REPOSITORY:TAG SIZE CREATED AT
mcp-installer-github-mcp-server:latest 59.5MB 2025-06-09 14:52:46 -0700 PDT
- Ports: {}
- Environment Variables: ['GITHUB_PERSONAL_ACCESS_TOKEN', 'GITHUB_TOOLSETS', 'GITHUB_DYNAMIC_TOOLSETS', 'GITHUB_READ_ONLY', 'GITHUB_HOST']
- Required Secrets: ['GITHUB_PERSONAL_ACCESS_TOKEN']
- Metadata: /Users/mossaka/.mcp-installer/servers/github-mcp-server/metadata.json
TO RUN THE CONTAINER (STDIO Transport):
1. Set required environment variables (if any):
export GITHUB_PERSONAL_ACCESS_TOKEN=your_actual_github_personal_access_token_here
2. Run the container interactively:
docker run -i --rm --name mcp-github-mcp-server-container -e GITHUB_PERSONAL_ACCESS_TOKEN=GitHub personal access token (required) -e GITHUB_TOOLSETS=Comma-separated list of toolsets to enable (optional) -e GITHUB_DYNAMIC_TOOLSETS=Set to 1 to enable dynamic tool discovery (optional) -e GITHUB_READ_ONLY=Set to 1 to enable read-only mode (optional) -e GITHUB_HOST=Custom GitHub API endpoint for GitHub Enterprise (optional) -e GITHUB_PERSONAL_ACCESS_TOKEN=${GITHUB_PERSONAL_ACCESS_TOKEN} mcp-installer-github-mcp-server
Note: This server uses STDIO transport (stdin/stdout communication).
- The container runs interactively (-i flag)
- It will be automatically removed when it exits (--rm flag)
- No port mapping needed as it uses standard input/output
3. To stop the container:
Ctrl+C in the terminal where it's running
4. For background operation with MCP client:
Use your MCP client to connect via subprocess/stdio
Great! The GitHub MCP server has been successfully installed. The installation completed successfully and built a Docker image.
Here's what was installed:
Server Name: github-mcp-server
Repository: https://github.com/github/github-mcp-server
Docker Image: mcp-installer-github-mcp-server:latest (59.5MB)
Transport Type: STDIO (communicates via standard input/output)
Required Configuration: The server requires a GITHUB_PERSONAL_ACCESS_TOKEN environment variable to authenticate with GitHub's API.
Optional Environment Variables:
GITHUB_TOOLSETS: Comma-separated list of toolsets to enable
GITHUB_DYNAMIC_TOOLSETS: Set to 1 to enable dynamic tool discovery
GITHUB_READ_ONLY: Set to 1 to enable read-only mode
GITHUB_HOST: Custom GitHub API endpoint for GitHub Enterprise
The server is now ready to use. To run it, you'll need to set your GitHub personal access token and then run the Docker container with the STDIO transport for communication with MCP clients.
After that, you can run docker
to run the container in your agent's MCP settings.
VS Code
"github": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN=<PAT>",
"mcp-installer-github-mcp-server",
]
}
Example (fetch server)
Prompt: "install https://github.com/modelcontextprotocol/servers/tree/typescript-servers-0.6.2/src/fetch"
I'll install the fetch MCP server from the specific path you provided.
sampling (MCP Server)
Input:
{
"url": "https://github.com/modelcontextprotocol/servers/tree/typescript-servers-0.6.2/src/fetch"
}
Output:
Successfully built Docker image for MCP server 'modelcontextprotocol-servers-fetch'!
Repository: https://github.com/modelcontextprotocol/servers/tree/typescript-servers-0.6.2/src/fetch
Location: /Users/mossaka/.mcp-sinstaller/servers/modelcontextprotocol-servers-fetch
DOCKER IMAGE:
- Generated new Dockerfile
- Image: mcp-sinstaller-modelcontextprotocol-servers-fetch
- Size & Created: REPOSITORY:TAG SIZE CREATED AT
mcp-sinstaller-modelcontextprotocol-servers-fetch:latest 654MB 2025-06-09 16:28:35 -0700 PDT
- Ports: {}
- Environment Variables: []
- Required Secrets: []
- Metadata: /Users/mossaka/.mcp-sinstaller/servers/modelcontextprotocol-servers-fetch/metadata.json
TO RUN THE CONTAINER (STDIO Transport):
1. Set required environment variables (if any):
No secrets required
2. Run the container interactively:
docker run -i --rm --name mcp-modelcontextprotocol-servers-fetch-container mcp-sinstaller-modelcontextprotocol-servers-fetch
Note: This server uses STDIO transport (stdin/stdout communication).
- The container runs interactively (-i flag)
- It will be automatically removed when it exits (--rm flag)
- No port mapping needed as it uses standard input/output
3. Use your MCP client to connect via subprocess/stdio transport
✅ Fetch MCP Server installed successfully!
The server has been built and is ready to use. Here are the key details:
Server Information:
Name: modelcontextprotocol-servers-fetch
Repository: https://github.com/modelcontextprotocol/servers/tree/typescript-servers-0.6.2/src/fetch
Transport: STDIO (standard input/output)
Image Size: 654MB
VS Code
"fetch": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"mcp-sinstaller-modelcontextprotocol-servers-fetch"
]
},
推荐服务器

Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。