Skip to content

Commit d6d8f55

Browse files
authored
Merge pull request github#3 from docker/text-updates
✏️ Text updates
2 parents d5290c5 + 26b2a0b commit d6d8f55

2 files changed

Lines changed: 89 additions & 25 deletions

File tree

CONTRIBUTING.md

Lines changed: 46 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,43 @@
1-
# Contributing to Docker MCP Registry
2-
1+
# 🤝 Contributing to Docker MCP Registry
32
Thank you for your interest in contributing to the official Docker MCP Registry.
43
This document outlines how to contribute to this project.
54

6-
## Pull request process
7-
8-
- All commits must include a Signed-off-by trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin.
5+
## 🔄 Pull request process overview
96
- Fork the repository to your own GitHub account and clone it locally.
10-
- Make your changes. To add a new MCP Server, create a new folder under `servers` with the name of your server and add a `server.yaml` inside.
11-
- Correctly format your commit messages, see Commit message guidelines below.
7+
- Repository includes a `servers` folder where you should add a new folder with a `server.yaml` inside.
8+
- Repository includes a `scripts` folder with bash scripts to automate some of the steps.
9+
- Correctly format your commit messages, see Commit message guidelines below. _Note: All commits must include a Signed-off-by trailer at the end of each commit message to indicate that the contributor agrees to the Developer Certificate of Origin._
1210
- Open a PR by ensuring the title and its description reflect the content of the PR.
1311
- Ensure that CI passes, if it fails, fix the failures.
1412
- Every pull request requires a review from the Docker team before merging.
1513
- Once approved, all of your commits will be squashed into a single commit with your PR title.
1614

17-
## Getting Started
18-
19-
You will need to provide:
15+
## 📋 Step-by-Step Guide
16+
### 1️⃣ Fork this repository
17+
Fork the repository to your own GitHub account and clone it locally.
2018

19+
### 2️⃣ Add your entry locally
20+
Add your entry by creating a new folder following the `owner@name` template, and create a `server.yaml` inside describing your MCP server. You will need to provide:
2121
- A valid name for your MCP
2222
- The GitHub URL of your project. The project needs to have a valid Dockerfile.
2323
- A brief description of your MCP Server.
24-
25-
Let's assume we have a new MCP Server to access my org's database. The MCP is called `My-ORGDB-MCP` and the GitHub repo is located at: https://github.com/myorg/my-orgdb-mcp We have created a bash script to simplify the creation process.
24+
- A category for the MCP server, one of:
25+
* 'ai'
26+
* 'data-visualization'
27+
* 'database'
28+
* 'devops'
29+
* 'ecommerce'
30+
* 'finance'
31+
* 'games'
32+
* 'communication'
33+
* 'monitoring'
34+
* 'productivity'
35+
* 'search'
36+
37+
#### 🚀 Generate folder and `server.yaml` using `new-server.sh` script
38+
You can use our script to automate the creation of the files. Let's assume we have a new MCP Server to access my org's database. The MCP is called `My-ORGDB-MCP` and the GitHub repo is located at: `https://github.com/myorg/my-orgdb-mcp`
39+
40+
You can call the tool passing the MCP server name, category, and github url.
2641

2742
```
2843
./scripts/new-server.sh My-ORGDB-MCP databases https://github.com/myorg/my-orgdb-mcp
@@ -65,26 +80,38 @@ source:
6580
# - param_name
6681
```
6782

68-
If you want to use a Docker image built by your organisation, you can pass it to the script as follows:
83+
If you want to provide a specific Docker image built by your organisation, you can pass it to the script as follows:
6984

7085
```
7186
IMAGE_NAME=myorg/myimage ./scripts/new-server.sh My-ORGDB-MCP databases https://github.com/myorg/my-orgdb-mcp
7287
```
7388

74-
As you can see, the configuration block has been commented out. If you need to pass environmental variables or secrets, please uncomment the
75-
necessary lines.
89+
As you can see, the configuration block has been commented out. If you need to pass environmental variables or secrets, please uncomment the necessary lines.
90+
91+
🔒 If you don't provide a Docker image, we will build the image for you and host it in [Docker Hub's `mcp` namespace](https://hub.docker.com/u/mcp), the benefits are: image will include cryptographic signatures, provenance tracking, SBOMs, and automatic security updates. Otherwise, self-built images still benefit from container isolation but won't include the enhanced security features of Docker-built images.
92+
93+
### 3️⃣ Run & Test your MCP Server locally
94+
🚧 tbd
95+
96+
### 4️⃣ Create `commit` and raise the Pull Request
97+
🚧 tbd
98+
99+
### 5️⃣ Wait for review and approval
100+
Upon approval your entry will be processed and it will be available in 24 hours at:
101+
- [MCP catalog](https://hub.docker.com/mcp)
102+
- [Docker Desktop's MCP Toolkit](https://www.docker.com/products/docker-desktop/)
103+
- [Docker Hub `mcp` namespace](https://hub.docker.com/u/mcp) (for MCP servers built by Docker)
76104

77-
## Testing your MCP Server
78105

79-
## Code of Conduct
106+
## 📜 Code of Conduct
80107

81108
This project follows a Code of Conduct. Please review it in
82109
[CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).
83110

84-
## Questions
111+
## Questions
85112

86113
If you have questions, please create an issue in the repository.
87114

88-
## License
115+
## 📄 License
89116

90117
By contributing, you agree that your contributions will be licensed under the MIT License.

README.md

Lines changed: 43 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,51 @@
1-
# Official Docker MCP Registry
1+
# 🐳 Official Docker MCP Registry
22

3-
## Contributing to the Docker MCP Registry
3+
Welcome to the Official Docker MCP (Model Context Protocol) Registry! This repository serves as a curated catalog of MCP servers that can be easily discovered, deployed, and integrated with any MCP Client and compatible with Docker tooling.
44

5-
We welcome contributions to the Official Docker MCP Registry! If you'd like to contribute, please review the [CONTRIBUTING](CONTRIBUTING.md) guide for details on how to get started.
5+
Entries in this catalog will be available at:
6+
- [MCP catalog](https://hub.docker.com/mcp)
7+
- [Docker Desktop's MCP Toolkit](https://www.docker.com/products/docker-desktop/)
8+
- [Docker Hub `mcp` namespace](https://hub.docker.com/u/mcp) (for MCP servers built by Docker)
69

7-
[TODO] Adding an MCP Server to the Docker Registry (why is good)
10+
## 🤖 What is MCP?
11+
The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect with external data sources and tools. Read more at [MCP Official Documantation](https://modelcontextprotocol.io/introduction).
812

9-
To modify or remove an MCP Server from the registry, please open an issue in this repository.
13+
## ✨ Why Use the Docker MCP Registry?
14+
- **Enterprise Security**: MCP servers built by Docker include cryptographic signatures, provenance tracking, and Software Bills of Materials (SBOMs) for maximum trust and compliance
15+
- **Container Isolation**: All MCP servers run in isolated containers, protecting your host system from potential security vulnerabilities
16+
- **Curated Quality**: All MCP servers undergo review to ensure they meet quality and security standards
17+
- **Easy Discovery**: Browse and find MCP servers for your specific use cases or share yours to millions of developers using Docker tools
18+
- **Docker Integration**: Seamless deployment with Docker containers
1019

11-
Any MCP Server that is not compliant, will be condemned and removed from the registry.
20+
## 🤝 Contributing to the Docker MCP Registry
21+
We welcome contributions to the Official Docker MCP Registry! If you'd like to contribute, you can submit a PR with the metadata information and it will be added to the [MCP catalog](https://hub.docker.com/mcp), to [Docker Desktop's MCP Toolkit](https://www.docker.com/products/docker-desktop/), and (for MCP servers images built by Docker) in `mcp` namespace in [Docker Hub](https://hub.docker.com/u/mcp).
22+
23+
To add your MCP server to the registry, please review the [CONTRIBUTING](CONTRIBUTING.md) guide for detailed instructions. We support two types of submissions:
24+
25+
### 🏗️ Option A: Docker-Built Official Image (Recommended)
26+
Have Docker build and maintain your server image with enhanced security features. You'll submit the required information via pull request and upon approval Docker will build, sign, and publish your image to mcp/your-server-name on Docker Hub and the catalog entry will be available in the catalog in 24 hours.
27+
28+
_**Benefits: Your image will include cryptographic signatures, provenance tracking, SBOMs, and automatic security updates**_
29+
30+
### 📦 Option B: Self-Provided Pre-Built Image
31+
In this option, you'll provide an already built image which will be used directly in the catalog.
32+
33+
_**Note: Self-built images still benefit from container isolation but won't include the enhanced security features of Docker-built images.**_
34+
35+
## ✏️ Modifying or Removing Servers
36+
To request modifications or removal of an existing MCP Server:
37+
1. For modifications: Submit a Pull Request with your proposed changes
38+
2. For removal requests: Open an issue explaining the reason for removal
39+
40+
## ✅ Compliance and Quality Standards
41+
All MCP servers in this registry must:
42+
- Follow security best practices
43+
- Include comprehensive documentation
44+
- Provide working Docker deployment
45+
- Maintain compatibility with MCP standards
46+
- Include proper error handling and logging
47+
48+
_**Non-compliant servers will be reviewed and may be removed from the registry.**_
1249

1350
## License
1451

0 commit comments

Comments
 (0)