Skip to content

Commit 39aa2b2

Browse files
ipedrazasipedrazas
authored
Merge pull request github#1 from docker/pr-proc-registry
chore: initial registry definition
2 parents b48c489 + 21080ac commit 39aa2b2

118 files changed

Lines changed: 3086 additions & 4 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎CONTRIBUTING.md‎

Lines changed: 65 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,17 +3,78 @@
33
Thank you for your interest in contributing to the official Docker MCP Registry.
44
This document outlines how to contribute to this project.
55

6-
## Getting Started
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.
9+
- 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.
12+
- Open a PR by ensuring the title and its description reflect the content of the PR.
13+
- Ensure that CI passes, if it fails, fix the failures.
14+
- Every pull request requires a review from the Docker team before merging.
15+
- Once approved, all of your commits will be squashed into a single commit with your PR title.
716

8-
Create an Issue in this repository using the `mcp-submission` [template](https://github.com/docker/mcp-registry/issues/new/choose).
17+
## Getting Started
918

1019
You will need to provide:
1120

1221
- A valid name for your MCP
13-
- The GitHub URL of your project
22+
- The GitHub URL of your project. The project needs to have a valid Dockerfile.
1423
- A brief description of your MCP Server.
1524

16-
The issue will start a manual process where your MCP Server will be reviewed, validated and, if macthes all the conditions, added to the repository and once all the tests pass, added to the registry.
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.
26+
27+
```
28+
./scripts/new-server.sh My-ORGDB-MCP databases https://github.com/myorg/my-orgdb-mcp
29+
```
30+
31+
This will create a directory under `servers` as follows: `./servers/my-orgdb-mcp` and inside you will find a `server.yaml` file with your MCP definition.
32+
33+
```
34+
server:
35+
name: test01
36+
image: mcp/test01
37+
type: server
38+
meta:
39+
category: test
40+
tags:
41+
- test
42+
highlighted: false
43+
about:
44+
title: test01
45+
icon: https://avatars.githubusercontent.com/u/182288589?s=200&v=4
46+
source:
47+
project: https://github.com/docker/mcp-registry
48+
branch: main
49+
# config:
50+
# description: TODO
51+
# secrets:
52+
# - name: test01.secret_name
53+
# env: TEST01
54+
# example: TODO
55+
# env:
56+
# - name: ENV_VAR_NAME
57+
# example: TODO
58+
# value: '{{test01.env_var_name}}'
59+
# parameters:
60+
# type: object
61+
# properties:
62+
# param_name:
63+
# type: string
64+
# required:
65+
# - param_name
66+
```
67+
68+
If you want to use a Docker image built by your organisation, you can pass it to the script as follows:
69+
70+
```
71+
IMAGE_NAME=myorg/myimage ./scripts/new-server.sh My-ORGDB-MCP databases https://github.com/myorg/my-orgdb-mcp
72+
```
73+
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.
76+
77+
## Testing your MCP Server
1778

1879
## Code of Conduct
1980

‎scripts/new-server.sh‎

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
#!/bin/bash
2+
3+
set -e
4+
5+
6+
NEW_SERVER_NAME=$(echo "$1" | tr '[:upper:]' '[:lower:]')
7+
NEW_SERVER_NAME_UPPER=$(echo "$1" | tr '[:lower:]' '[:upper:]')
8+
9+
PATH_TO_SERVER="./servers/$NEW_SERVER_NAME"
10+
CATEGORY=$(echo "$2" | tr '[:upper:]' '[:lower:]')
11+
12+
# IF IMAGE_NAME IS NOT PROVIDED, USE THE DEFAULT ONE
13+
IMAGE_NAME=${IMAGE_NAME:-"mcp/$NEW_SERVER_NAME"}
14+
15+
16+
if [[ -f "$NEW_SERVER_NAME" ]]; then
17+
echo "❌ File already exists: $NEW_SERVER_NAME"
18+
exit 1
19+
fi
20+
21+
echo "Creating new server: $NEW_SERVER_NAME"
22+
23+
mkdir -p "$PATH_TO_SERVER"
24+
25+
echo "Server created successfully"
26+
27+
echo "Creating server.yaml"
28+
29+
echo "server:
30+
name: $NEW_SERVER_NAME
31+
image: $IMAGE_NAME
32+
type: server
33+
meta:
34+
category: $CATEGORY
35+
tags:
36+
- $CATEGORY
37+
highlighted: false
38+
about:
39+
title: $NEW_SERVER_NAME
40+
icon: https://avatars.githubusercontent.com/u/182288589?s=200&v=4
41+
source:
42+
project: $3
43+
branch: main
44+
# config:
45+
# description: "TODO"
46+
# secrets:
47+
# - name: $NEW_SERVER_NAME.secret_name
48+
# env: $NEW_SERVER_NAME_UPPER
49+
# example: "TODO"
50+
# env:
51+
# - name: ENV_VAR_NAME
52+
# example: "TODO"
53+
# value: '{{$NEW_SERVER_NAME.env_var_name}}'
54+
# parameters:
55+
# type: object
56+
# properties:
57+
# param_name:
58+
# type: string
59+
# required:
60+
# - param_name
61+
62+
" > "$PATH_TO_SERVER/server.yaml"
63+
64+
echo "$NEW_SERVER_NAME created successfully"
65+

‎servers/SQLite/server.yaml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
name: SQLite
2+
image: mcp/sqlite
3+
type: server
4+
meta:
5+
category: database
6+
tags:
7+
- sqlite
8+
- database
9+
about:
10+
title: SQLite (Archived)
11+
description: Database interaction and business intelligence capabilities.
12+
icon: https://avatars.githubusercontent.com/u/48680494?v=4
13+
source:
14+
project: https://github.com/modelcontextprotocol/servers
15+
branch: 2025.4.24
16+
directory: src/sqlite
17+
run:
18+
command:
19+
- --db-path
20+
- /mcp/db.sqlite
21+
volumes:
22+
- mcp-sqlite:/mcp

‎servers/astra-db/server.yaml‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
name: astra-db
2+
image: mcp/astra-db
3+
type: server
4+
meta:
5+
category: database
6+
tags:
7+
- astra-db
8+
- database
9+
highlighted: true
10+
about:
11+
title: Astra DB
12+
icon: https://avatars.githubusercontent.com/u/573369?s=200&v=4
13+
source:
14+
project: https://github.com/datastax/astra-db-mcp
15+
branch: refs/pull/14/merge
16+
config:
17+
description: Configure the connection to Astra DB
18+
secrets:
19+
- name: astra-db.application_token
20+
env: ASTRA_DB_APPLICATION_TOKEN
21+
example: your_astra_db_token
22+
env:
23+
- name: ASTRA_DB_API_ENDPOINT
24+
example: ""
25+
value: '{{astra-db.endpoint}}'
26+
parameters:
27+
type: object
28+
properties:
29+
endpoint:
30+
type: string

‎servers/atlas-docs/server.yaml‎

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
name: atlas-docs
2+
image: mcp/atlas-docs
3+
type: server
4+
meta:
5+
category: devops
6+
tags:
7+
- atlas-docs
8+
- devops
9+
about:
10+
title: Atlas Docs
11+
icon: https://avatars.githubusercontent.com/u/184709581?s=200&v=4
12+
source:
13+
project: https://github.com/CartographAI/atlas-docs-mcp
14+
branch: master
15+
config:
16+
description: Configure the connection to Atlas Docs
17+
env:
18+
- name: ATLAS_API_URL
19+
example: https://atlas.cartograph.app/api
20+
value: '{{atlas-docs.api_url}}'
21+
parameters:
22+
type: object
23+
properties:
24+
api_url:
25+
type: string

‎servers/atlassian/server.yaml‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
name: atlassian
2+
image: mcp/atlassian
3+
type: server
4+
meta:
5+
category: productivity
6+
tags:
7+
- atlassian
8+
- confluence
9+
- jira
10+
highlighted: true
11+
about:
12+
title: Atlassian
13+
description: Tools for Atlassian products (Confluence and Jira). This integration supports both Atlassian Cloud and Jira Server/Data Center deployments.
14+
icon: https://avatars.githubusercontent.com/u/43281909?s=200&v=4
15+
source:
16+
project: https://github.com/sooperset/mcp-atlassian
17+
branch: v0.11.2
18+
config:
19+
description: The MCP server is allowed to access these paths
20+
secrets:
21+
- name: atlassian.confluence.api_token
22+
env: CONFLUENCE_API_TOKEN
23+
example: your_api_token
24+
- name: atlassian.confluence.personal_token
25+
env: CONFLUENCE_PERSONAL_TOKEN
26+
example: your_api_token
27+
- name: atlassian.jira.api_token
28+
env: JIRA_API_TOKEN
29+
example: your_api_token
30+
- name: atlassian.jira.personal_token
31+
env: JIRA_PERSONAL_TOKEN
32+
example: your_api_token
33+
env:
34+
- name: CONFLUENCE_URL
35+
example: https://your-company.atlassian.net/wiki
36+
value: '{{atlassian.confluence.url}}'
37+
- name: CONFLUENCE_USERNAME
38+
example: your.email@company.com
39+
value: '{{atlassian.confluence.username}}'
40+
- name: JIRA_URL
41+
example: https://your-company.atlassian.net
42+
value: '{{atlassian.jira.url}}'
43+
- name: JIRA_USERNAME
44+
example: your.email@company.com
45+
value: '{{atlassian.jira.username}}'
46+
parameters:
47+
type: object
48+
properties:
49+
confluence:
50+
type: object
51+
properties:
52+
url:
53+
type: string
54+
username:
55+
type: string
56+
required:
57+
- url
58+
jira:
59+
type: object
60+
properties:
61+
url:
62+
type: string
63+
username:
64+
type: string
65+
required:
66+
- url
67+
anyOf:
68+
- required:
69+
- confluence
70+
- required:
71+
- jira

‎servers/audiense-insights/server.yaml‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
name: audiense-insights
2+
image: mcp/audiense-insights
3+
type: server
4+
meta:
5+
category: devops
6+
tags:
7+
- audiense-insights
8+
- devops
9+
about:
10+
title: Audiense Insights
11+
icon: https://avatars.githubusercontent.com/u/2454008?s=200&v=4
12+
source:
13+
project: https://github.com/AudienseCo/mcp-audiense-insights
14+
config:
15+
description: Configure the connection to Audiense Insights
16+
secrets:
17+
- name: audiense-insights.client_secret
18+
env: AUDIENSE_CLIENT_SECRET
19+
example: your_client_secret_here
20+
- name: audiense-insights.twitter_bearer_token
21+
env: TWITTER_BEARER_TOKEN
22+
example: your_token_here
23+
env:
24+
- name: AUDIENSE_CLIENT_ID
25+
example: your_client_id_here
26+
value: '{{audiense-insights.client_id}}'
27+
parameters:
28+
type: object
29+
properties:
30+
client_id:
31+
type: string
32+
required:
33+
- client_id

‎servers/aws-cdk-mcp-server/server.yaml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
name: aws-cdk-mcp-server
2+
image: mcp/aws-cdk-mcp-server
3+
type: server
4+
meta:
5+
category: devops
6+
tags:
7+
- aws-cdk-mcp-server
8+
- devops
9+
about:
10+
title: AWS CDK
11+
description: AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.
12+
icon: https://avatars.githubusercontent.com/u/3299148?v=4
13+
source:
14+
project: https://github.com/awslabs/mcp
15+
directory: src/cdk-mcp-server

‎servers/aws-core-mcp-server/server.yaml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
name: aws-core-mcp-server
2+
image: mcp/aws-core-mcp-server
3+
type: server
4+
meta:
5+
category: devops
6+
tags:
7+
- aws-core-mcp-server
8+
- devops
9+
about:
10+
title: AWS Core MCP Server
11+
description: Starting point for using the awslabs MCP servers.
12+
icon: https://avatars.githubusercontent.com/u/3299148?v=4
13+
source:
14+
project: https://github.com/awslabs/mcp
15+
directory: src/core-mcp-server

‎servers/aws-diagram/server.yaml‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
name: aws-diagram
2+
image: mcp/aws-diagram
3+
type: server
4+
meta:
5+
category: devops
6+
tags:
7+
- aws-diagram
8+
- devops
9+
about:
10+
title: AWS Diagram
11+
description: Seamlessly create diagrams using the Python diagrams package DSL. This server allows you to generate AWS diagrams, sequence diagrams, flow diagrams, and class diagrams using Python code.
12+
icon: https://avatars.githubusercontent.com/u/3299148?v=4
13+
source:
14+
project: https://github.com/awslabs/mcp
15+
directory: src/aws-diagram-mcp-server

0 commit comments

Comments
 (0)