
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"
]
},
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.